PT
☰

pendo.io

Endereço IP 34.54.74.243
DNS gerenciado por Google
E-mail Configurado
Registros 52

O domínio pendo.io responde no endereço IP 34.54.74.243. Esse endereço pertence à Google Cloud, sediada em Estados Unidos. O DNS do domínio é gerenciado por Google, que define para onde aponta cada subdomínio. O e-mail de pendo.io passa por 5 servidores; o de maior prioridade é aspmx.l.google.com. Também publica 41 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

  • atlassian-domain-verification=haPUq2rY+fPmNyu5fCrMq257k+26DqpNo9RZonaEq31aGzPNg5S8bjEB9qCkF1W+ 600s
  • google-site-verification=fPkSOGYZ4k7ffyV--3vklUU12CCFE35fzsuN2DHrXCQ 600s
  • v=spf1 include:docebosaas.com redirect=4i2em5lw._spf._d.mim.ec 600s
  • jamf-site-verification=vXIgUTgcCbUEbMiSCYjAbQ 600s
  • postman-domain-verification=5a0882a7e870d944720a28f3576aff39f3fb5a169bf627a29a5b2201002f21d6e4d34bd26fa5755f4aebbbe7c51ff87f3cb8db36fdcb944f98079b72cb913ab4 600s
  • MS=ms84958166 600s
  • zapier-domain-verification-challenge=8e7e5d59-5fad-4b5c-a361-9b19428e57a0 600s
  • whimsical=3ec496061464753b3c4e4a1e34feac015f854d8e 600s
  • exec-domain-verification-vaq9ng=uNiKN8MHFlywTBRkmaZ18sG4S 600s
  • firebender-domain-verification-tc16df=lyWtx3eHvp6NLJjUGhW4VI6WL 600s
  • anthropic-domain-verification-78fd6n=cXpPTpUsDj0GQNSovbiAXGwXw 600s
  • miro-verification=ff002c24dc72e8902e28e6aa247e42868e0d2a25 600s
  • apple-domain-verification=ySUpulB6B62zv6Ww 600s
  • facebook-domain-verification=6jt10dejylph4fztu78gwqv5antj2b 600s
  • monday-com-verification=M4MtfvOAqbYu5xXLhLtLhLa38dNlW1CEcuk0FPk5uB0 600s
  • ciscocidomainverification=1f043413f07365263c5255f63181045759a7c1a78b2c23c5123fea3b1b4e6b98 600s
  • drift-domain-verification=734746d7bf20a9137c09d8378597500c0bff59112bc3b8a093b1d1026c33c050 600s
  • hubspot-developer-verification=YjU0OTM2ZDUtOTE2Mi00OTRjLTg1OTUtZjUwYjU4OGI2Mjcz 600s
  • intacct-esk=4FED1A3DEF352267E0539E06A8C05A57 600s
  • google-site-verification=qLYyf7z5PQFG8HUEYiUxZkIsW8G73iV2Y7xwKsQ0qW0 600s
  • cursor-domain-verification-g98gs7=9qnwJidCmu0UjFvCd2jjqfjRs 600s
  • google-site-verification=lb0sv1si4u-tR4-WWUKviO2a9U_MqmFGWUmoTBOGqIk 600s
  • adobe-idp-site-verification=0464dd56ff69a077c0d8bbee8c8e245f68bd411122030377922ada1165f299f0 600s
  • calendly-site-verification=NHZ9h1kJ3t1uxXVIXjAhSVQfMX7zvI5RCUYwd0fGo 600s
  • MS=ms91173086 600s
  • google-site-verification=j0tbz4tWi3ZRcRtIhhmZYnj078u2D6Szb3Iu4pNxKSA 600s
  • openai-domain-verification=dv-PlU1U64r3swfbfEnu4Wyfzh2 600s
  • notion-domain-verification=kJSlM8YgYQevzjt4AtIvjRrqKaXmwfgDVTB0Uo0k2OX 600s
  • lovable_verification=Ne4SpW7BBluYqPe2CqYy 600s
  • atlassian-sending-domain-verification=6946296c-d333-49c5-b6e5-7895395b9696 600s
  • google-site-verification=5OtJq8mihvORFOGT6ZrjGC_uWEu-u6KadYco8qSSwHA 600s
  • atlassian-domain-verification=pbhYuoWU4/Id50c7Qip7Ctz+xrBsfxExovTYEFxV8figd7KU1vhm6TndYJ5LMKxA 600s
  • linear-domain-verification=qyakyx4sk5qs 600s
  • slack-domain-verification=OCwewNvPyVSZLlwapK5Ld9xptTdZA3DmB9LDYBDI 600s
  • smartsheet-site-validation=mEUq4iTotvqt5XiijvT_eAK1ADFQufCu 600s
  • google-site-verification=8c0OnIZ8BAC-QE6t0vOgHSsouB_nNVI7t2efTkpsg_w 600s
  • MS=ms84486845 600s
  • docusign=144e8912-1f35-42ea-9b7c-1c0f3350d15e 600s
  • google-site-verification=nI02dbcexFrTJKuMdoCMTK9JOVFuFIy2TZXjYgpt9ag 600s
  • wrike-verification=MjM2NDQ3MDo1NDI2NTJiZDZkZDFlMmFjYTU3ZmUyNTZkZmYzNDFjOWM1YTNhOTZlMDgyMTQ0ZGIxYzY3NTBmYWRmZWRhM2Zh 600s
  • google-site-verification=gdDeZOTUsarQhSseL_vL3b107YpdqDwRP2aAtJxDiNw 600s

SOA Registros SOA

  • ns-cloud-e1.googledomains.com 21600s

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