☰
PT
Android iOS

yelp.com

Endereço IP 146.75.116.116
DNS gerenciado por NS1
E-mail Configurado
Registros 57

O domínio yelp.com responde no endereço IP 146.75.116.116. O DNS do domínio é gerenciado por NS1, que define para onde aponta cada subdomínio. O e-mail de yelp.com passa por 5 servidores; o de maior prioridade é aspmx.l.google.com. Também publica 42 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

  • pardot813133=a90e85640d4bb5a429d171325168640bb9463489071367d9615ebc73919f1bbb 3600s
  • stripe-verification=6CB8483E931BB30A9798D497914DB00B6CD935BC954C67CB31EC582361636F3F 3600s
  • facebook-domain-verification=mdu6515tt8odq7akwzr4a036q6w3cz 3600s
  • wrike-verification=NDA1MDgyNTpiMDcyYWNmMjgyYmEzOWFhNDE3NzA1YTE1NGFmYmYzYmU0Y2IxNGQwNTA5YzNkMDIyNWVkYmNhZDMwZmQ5ZTM1 3600s
  • _globalsign-domain-verification=PO95qR5HARP3zbvcQ1WFBVyLGBUvgjmgc16ENjCtmy 3600s
  • status-page-domain-verification=z80f59yz1jkt 3600s
  • aline-domain-verification-d4fg3g=dSnUs4LT4OucL5MIUWA1pqjnF 3600s
  • atlassian-domain-verification=k//LP2aSAEPqGqlbOWy3YhbF21wtfSXibOk0vz6Dx1BV3du/Ub/Fyiv3C55m2vkS 3600s
  • google-site-verification=4OznISzbxHzmhzRM-NtpUcP1P6nIfsanNZdNI1G_EU8 3600s
  • notion-domain-verification=WDNH0Y6wClSmazu1ox2mB6gcdkjd6MA3er4OAerRCUt 3600s
  • jamf-site-verification=LcGrLBerA2Rm4ZTuGWhAQw 3600s
  • status-page-domain-verification=f3txhd81xn94 3600s
  • status-page-domain-verification=kl0pq45qyb3d 3600s
  • atlassian-sending-domain-verification=b8aeb8b2-f866-4573-9468-2b248ab4d392 3600s
  • apple-domain-verification=7xkVWehEYAdxIGR18-iBcC-263XTlJE3Xh4KZcgF_1o 3600s
  • gm36n17d8y8544hg7s3n5ptcjgzfb17f 3600s
  • google-site-verification=NOSls2JfXI55tW5qFU89NY93kA8LB6YTHGBzCFz3cy8 3600s
  • openai-domain-verification=dv-fJLMFcavOatIU9F5VNTB4uzC 3600s
  • have-i-been-pwned-verification=dweb_7pqrwg9nyaw5qzccmdpbh43e 3600s
  • adobe-idp-site-verification=9ac7165b0af2483ec7767a476cdba5d35ebf9581d5696dc420fb058f9a7372af 3600s
  • dtm-domain-verification=jLI9ztu7vQd32GYHfJfjNbjuGdSdJk7jzYeLmaZKEHs 3600s
  • status-page-domain-verification=560td8k1wdsc 3600s
  • google-site-verification=3lJN-zw-10jb4bLfmXsqFizDALMsnlhqZ-TPG-AjHWU 3600s
  • 0jw2h0bjphcxmg3snr0fjg270ysc0wgk 3600s
  • google-site-verification=-Y773kzVn1DQlVG-Ugprk7qDuZdki_5cqljezw1daiU 3600s
  • cursor-domain-verification-bybp9b=u4Ql3DroYKAYNKZO7GMmm7CN6 3600s
  • zapier-domain-verification-challenge=6da7ad16-5f37-4d23-a121-259dae5492de 3600s
  • atlassian-domain-verification=45ozypIxFMV4A0xxbgkqTjhHaKzj8CrbxzUxbakhomBdkM6bzr117OBkfPJJlbAX 3600s
  • mixpanel-domain-verify=277018fd-af0f-4112-bc98-ec0aa09c9e62 3600s
  • _globalsign-domain-verification=_64UG15h1zSn86m51pRb3vaFMDTtUCsP2RBUJ7DAAM 3600s
  • cloudflare_dashboard_sso=9d6accac4ddd9be2d5930b92acfdb0a5 3600s
  • zoho-verification=zb51277094.zmverify.zoho.com 3600s
  • google-site-verification=-LX_luQh_Kq5PPMW-YLBGAr22sLmB9uXTZDZYwWdWcc 3600s
  • google-site-verification=GRQLNPjWLxGr_Ka6phLFqBXooCAZt35ZZz2ZV5JNsDQ 3600s
  • citrix-verification-code=1dee59ff-c292-47a1-8faf-a0c7803c742a 3600s
  • _46ivs5dmhmqu8fah0jyafidcgnb16m8 3600s
  • datadome-domain-verify=XwAuoddrKPKQX4hiaY3MmiM7bnaIFuJv 3600s
  • onetrust-domain-verification=53afac8ba50845c3b7c8ba137d2349c0 3600s
  • v=spf1 include:everbridge.net include:yelp.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all 3600s
  • sending_domain1084122=a5612a391e2e2b3d3cc46238b2e038b211048e6e45cc04d0947989d5e4f8833c 3600s
  • apple-domain-verification=qa3GTY5z2ELxESie 3600s
  • profound-domain-verification-98wkep=o4E7iCuctO9gpJqyfkrCLFqXp 3600s

SOA Registros SOA

  • dns1.p06.nsone.net 60s

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á 9 horas.