newrelic.com
O domínio newrelic.com responde no endereço IP 151.101.194.217. Esse endereço pertence à Fastly, Inc., sediada em Canada. O e-mail de newrelic.com passa por 3 servidores; o de maior prioridade é aspmx.l.google.com. Também publica 40 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
- 151.101.194.217 2829s
- 151.101.130.217 2829s
- 151.101.2.217 2829s
- 151.101.66.217 2829s
MX Registros MX
- 10 aspmx.l.google.com 3358s
- 20 alt1.aspmx.l.google.com 3358s
- 30 alt2.aspmx.l.google.com 3358s
NS Registros NS
- ns02.nr-dns.net 13881s
- ns03.nr-dns.net 13881s
- dns3.p07.nsone.net 13881s
- ns01.nr-dns.net 13881s
- dns1.p07.nsone.net 13881s
- ns04.nr-dns.net 13881s
- dns4.p07.nsone.net 13881s
- dns2.p07.nsone.net 13881s
TXT Registros TXT
- google-site-verification=IzCrXIx1zpSj5z3EI6pOU5cQjCyT-BuTfrwgdRfURS0 3600s
- amazonses:nDexZmfBiV9Hs3b3/uSImeSqxQt+lkhWIaN5tMeykDI= 3600s
- adobe-idp-site-verification=b1e661c3d47470de728c17470365d00226531208a3b078435f99c4f578e6d88f 3600s
- amazon-business-verification=6e7f1b9714397b936922514be022b98f5b42d792a902bc9cddd38b88cd44deea 3600s
- _416n6vjfagebu88vjkhqdantavu7bio 3600s
- parallels-domain-verification=dfa9e5d1d119426d88a6f095b19b74173031c3044b054d23893f7d346a1bd70b 3600s
- amazonses:d1f5E6eNonJ2cHLr+o1Xkc8NZ1I8OKHGh6N2DwDTAb0= 3600s
- jetbrains-domain-verification=8u26rngyc6u5p4xt0rma5cmjd 3600s
- google-site-verification=LoR9AZ42PtO0eDHfnqn00jeAoZcgnx07h_ZfGvaeOrs 3600s
- atlassian-domain-verification=7FqXvSclqkqVwfobk6I1XpfqGI7J7/rHNrSMMImW5NUeNabcbL0jFMedahzCorWL 3600s
- zoom-domain-verification=ZOOM_verify_de26cf3a37e943b491661f2d084c07d5 3600s
- whimsical=1086557391c5fca3541fc0e214591ce10420eef4 3600s
- google-site-verification=YRMSthamK49wTIo72yB89R2aEIBECJ11n7165rDzfsE 3600s
- pardot893801=31820b7b0c868e8426e1f8ebf51ca209f26b9388a7169f79a1ab29d640d84650 3600s
- docker-verification=b2502828-def0-4401-a612-840e41402b0f 3600s
- DabVBALwhfo3bwvQBZHzf39MO8w 3600s
- wework-site-verification=KPdt0l0h4yCgRIWd 3600s
- neat-pulse-domain-verification-jM2BKzM=3a7955da-c4e9-44e7-b5ed-185dad4b831d 3600s
- onetrust-domain-verification=d903445ef59c4a08a5098067e40dd86b 3600s
- apple-domain-verification=7Er7DKxKjTdmiJ4v 3600s
- 28wk3142yk508gjqpr27hhf69lwhg0wv 3600s
- figma-domain-verification=5b03cbc8f270820103e1485a4d673cef0b5a2364a8643b252d5f30a1336551c2-1718813534 3600s
- a07ddd918db549a2a6d356b2980627e6 3600s
- v=spf1 ip4:54.214.46.183/32 ip4:38.129.65.12/32 ip4:149.72.209.60/32 include:mktomail.com include:_spf.google.com include:mailgun.org include:docebosaas.com include:_spf.qualtrics.com include:bea9fd.workshop-spf.net ~all 3600s
- mongodb-site-verification=zKrp4m6CLWVIeTlSRz7gZuaatxim0wkp 3600s
- v=MCPv1; k=ed25519; p=uTemv+O2h9im1ONfJTXBGQ0g2hP9tXgDhf3lmzBT/PE= 3600s
- docusign=469d6b53-4bae-4d27-8883-1f0c697ad722 3600s
- jamf-site-verification=sgVAml6f0b_jjl_Y9vCkXA 3600s
- gradle-verification=OI7J4VVAO5BJR4FB13URU9HLM4UB1 3600s
- google-site-verification=mL6p92_GRtlQoOU_JiL3Wd-JE3LFVfkiUXrjFsH7-hk 3600s
- _26piw9y0krk9y7w6cl4wxe3ppfyztuw 3600s
- google-site-verification=OOuGwQ__672RAHPGeoxpR6S5yZSkgnPQrUrSL4zRSXA 3600s
- _globalsign-domain-verification=4F75HIXJYgIp1lJKOK40HSdTb5jUc09eGA2yrgx5kz 3600s
- yandex-verification: fc1dd009c32ab111 3600s
- google-site-verification=0d_0kFVMJo8U1btxjxO4F-VFMmOAnNT3fGBXhePls1A 3600s
- google-site-verification=IcoYxGaPyPWM0lNynfgRn7JhkpaXprYeUxWWXXurE20 3600s
- cursor-domain-verification-s0zc1a=cWBKNqCIhpeh5aDFJCf7qS6s6 3600s
- spf2.0/pra ?all 3600s
- anthropic-domain-verification-7pw3ks=z8p1hYKMVFTWa6Bwm5cQHo7OD 3600s
- qzq5wlt1920x4rd538hpqznblcy9n91g 3600s
SOA Registros SOA
- dns1.p07.nsone.net 3600s
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á 4 horas.