PT
☰

doubleverify.com

Endereço IP 199.60.103.165
DNS gerenciado por Akamai
E-mail Configurado
Registros 55

O domínio doubleverify.com responde no endereço IP 199.60.103.165. Esse endereço pertence à HubSpot, Inc., sediada em Estados Unidos. O DNS do domínio é gerenciado por Akamai, que define para onde aponta cada subdomínio. O e-mail de doubleverify.com passa por 2 servidores; o de maior prioridade é mxa-005c0b02.gslb.pphosted.com. Também publica 44 registros TXT, usados para verificar a propriedade do domínio em serviços externos e para configurar a segurança do e-mail com SPF, DKIM e DMARC.

A Registros A

MX Registros MX

NS Registros NS

TXT Registros TXT

  • eipq6b8b7g1op6gpohrl04u8c9 90s
  • dropbox-domain-verification=vq0003kxspf2 90s
  • google-site-verification=3NIJJy8B-jPLKM6_ubj_Q4R7KyMB_8K167-va6Ea7Sg 90s
  • postman-domain-verification=9f619f012c271146a30289c5bf9c4b036fbc3e31ffc644c675dede0b49ce48ac35c3954e8d2df842025e31d5a4162401ae9643dbba5ffea15243a4fdb13e9757 90s
  • Probe.ly=73e000a9-a5df-48a5-a8f6-f4f6cee5e2ad 90s
  • MS=ms13378337 90s
  • google-site-verification=xoL8bdppyhgtVfkgs4cDeJIoDPQPg8x6C1YQerjksHg 90s
  • uber-domain-verification=75fa8f40-89cf-4918-9611-30c80db130b1 90s
  • abuseipdb-verification=VGYlkw6Q 90s
  • docusign=085e7679-8929-4902-96f0-77b5f36ed535 90s
  • miro-verification=37c157ec056714cd8093465ce52fb881c36d13dd 90s
  • figma-domain-verification=80c9c654e7c18602ab0d41343f68c94dff3a26d4a3d2ff1fd2f6431490ac6371-1754320112 90s
  • anthropic-domain-verification-n9kpp6=x3uODB3u9pluExGeSvnMnNu9D 90s
  • v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all 90s
  • atlassian-domain-verification=NaCxqlNT6zkIChXfg5gzj3cOWHQK7hzrqei/lYM7Sg9/pbWndaMuDwjKZJBxv1s9 90s
  • docusign=1abeb306-299a-451b-8e2d-e48b433eba0f 90s
  • adobe-idp-site-verification=5777e7077aa021fff13a14be21f34a2e63cdb5a9fe91bc13995b730ff12c94c8 90s
  • tinfoil-site-verification: 07368c6d6911b8038f617dd518501a5654d5d08a=12c7c6ac968a7992c0450370d2bd6a6d422c459d 90s
  • google-site-verification=OjtVno32jIZGrZs_rFhWNx9V2VYjWgupz_WqTcehje8 90s
  • jetbrains-domain-verification=eazcd0noqv6hwga0hjrblh4vi 90s
  • cursor-domain-verification-1wnytz=GI7qmTy0E9CWWjkuuN9ivuUtb 90s
  • jamf-site-verification=Ebcn7fBTU4lQFL7DGzzr1w 90s
  • northpass-domain-verification=ae825879144ab624ebcda7a08276ee04 90s
  • MS=9235921E61AE6D9F1A514BD1562DF6929212AD4A 90s
  • b21ad0gkalu97i05vd4ohtrq0p 90s
  • canva-site-verification=4E3AiC01BuQI6dk2iaRETQ 90s
  • google-site-verification=BQjfne_GAus5wkarvtRrAMRIl1XM1Nnpor8kby8jPRM 90s
  • kmhttr9bu4pp6vpi78p5l91fsc 90s
  • mongodb-site-verification=0ABzrJtBKQCDqL5XioMeERYPpmZR5NCX 90s
  • MS=459662B08FE7ABE5CD420C8A0DA91B47F187B31A 90s
  • ZOOM_verify_eRV87FRgSGeEEEdLh5Js1g 90s
  • pendo-domain-verification=UgO-HNJWEFrV9IlVMnOwhvRFCFE 90s
  • google-site-verification=iVrwH6-iIeT2rnheK2ocsVTfvLosfanyJ4hEgnFWlHI 90s
  • notion-domain-verification=Z2D0SFJsOZXQZ3JXOX9QCaUGLSPZSH4psgHTitrkM2 90s
  • e9ae689e51780de2c0b9345581b12b339cf0762531ac7ecf66b924d128409aa 90s
  • hcp-domain-verification=371d48d56f5582be8b86a87b94ce5f9bc0ae4dae4321c67d4ce49437432fc1a8 90s
  • atlassian-domain-verification=HYtLFBZ74v9/kJSRXvExAUfmlR30L2kE7vr66ADGgF5tOVNCxz1aaDdgIdqoo6yk 90s
  • atlassian-domain-verification=HjhlR3SDqq8UtKGvvXbYPGi4DhIGJv+m+Dz0pgPI2h2XaGUqwc+NgeJ73rmFZwLG 90s
  • zapier-domain-verification-challenge=ab209f91-f279-4b1d-8092-10b85e0eca02 90s
  • openai-domain-verification=dv-ggQyYeYflbMrGNMgDEIIXA1F 90s
  • 1password-site-verification=RHJFOJLIFVDHLEB6XDVGNUTQD4 90s
  • docusign=470a15ee-dd4a-4ede-9dcd-fbe1eeb3b8cd 90s
  • apple-domain-verification=t3JvA54ZdhjAFCq8 90s
  • docker-verification=aa08f590-81a9-482f-97a8-a8c78d07fe77 90s

SOA Registros SOA

  • a1-100.akam.net 900s

O que significa cada registro

  • A e AAAA: o endereço IP do servidor, em IPv4 e IPv6.
  • MX: os servidores que recebem o e-mail do domínio. O número é a prioridade; o menor é tentado primeiro.
  • NS: os servidores de nomes, que têm a palavra final sobre o DNS do domínio.
  • TXT: texto livre. Usado sobretudo para SPF, DKIM e DMARC, e para verificar a propriedade perante terceiros.
  • TTL: por quantos segundos o dado pode ficar em cache antes de perguntar de novo.

Consultado há 20 horas.