PT
☰

grainger.com

Endereço IP 23.36.162.220
DNS gerenciado por Akamai
E-mail Configurado
Registros 54

O domínio grainger.com responde no endereço IP 23.36.162.220. Esse endereço pertence à Akamai Technologies, sediada em Germany. O DNS do domínio é gerenciado por Akamai, que define para onde aponta cada subdomínio. O e-mail de grainger.com passa por 1 servidores; o de maior prioridade é grainger-com.mail.protection.outlook.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

  • citrix-verification-code=459fd158-7ff0-413a-89f9-11f4adaa6cf9 300s
  • _6xiimcye290g0hjo5rye9ejmk47p3rl 300s
  • EmnRu/y8GTb6+7yQi5xlofM29PClXiDi9J2xBS75RrBVjtAXyPeA3csvzuLLUK2L+ayXEZiwDSETbkMgVQZchA== 300s
  • _enmptnx1kfnurop4wgr2lh2qhkq9spz 300s
  • adobe-idp-site-verification=b4c26bca07a3105580a50a225ee55407eba116b7e49a4914a9f441e528e2b4c9 300s
  • figma-domain-verification=e84b981a7df159e7d49fa245bbd89b4203a2d1cf7c57cfb92af35485e9215301-1733430706 300s
  • MS=ms23701922 300s
  • _2jlc6msxcze54givbfp4c1ylsjdhe5b 300s
  • openai-domain-verification=dv-1YcJmghw54cdPW0XbobTv5Zs 300s
  • jetbrains-domain-verification=8g70luojzuk5zc9q5errae4l3 300s
  • wmsz7935tb2w8t9vlx152mzdxs75ty89 300s
  • successfactors-site-verification=MGY0YzA5YjVhMGI3OTcwNDBkM2FlNjdjNTUwYmQ5Y2IxM2Q2MTdkNjAxZWRiYjJhOWI1ZGQ4NzNhOWJlYTZkNg== 300s
  • hz76t1x6mhv6hbcmvfdr6zyvtw0w1ztf 300s
  • google-site-verification=SvkXr1PivJTyI5hzMCL-XQ6qeAn0pRlx69BJ5_MEqtg 300s
  • facebook-domain-verification=409qgr9quabcxc2jh5ephx4h1o4jis 300s
  • pardot_288512_*=55c0ce6200d25361f1fe7e9d12654fce5a08ec7b52a9d1b7b5b643f9f3997047 300s
  • atlassian-domain-verification=fO4OAB/yF/HDdp96NPfnfPZsoqRJjGgU2c75Kj4wNThRQHPbaOouabu2fXFFC81s 300s
  • 00D0R0000008e3Y=1TBDV000000CaRC 300s
  • windsurf-verification=WEeWfsxEbSRRsXdQwilNVwi4R4Sv2SCAQ8yfz9fn890= 300s
  • hcp-domain-verification=86ca61ceeff0076f600ae346949fc4c99469792b13d29d5173444072e7663c0d 300s
  • v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all 300s
  • datadome-domain-verify=NmgeBPELTMBGA3n460SXHV2SM25HXfwP 300s
  • 00Di0000000ivUT=1TBKc0000000006 300s
  • 1KtuPMsFIYbBWXueRpUHE67lYJXdqXhTgRTfPTsWgSextXMOmUxPS+B/1+A/fKVHnvgYHoWTpgTU9lSuIO1nvQ== 300s
  • 00D8L0000000MeZ=1TBhG0000000001 300s
  • apple-domain-verification=apU2Xty3qe9beQA6 300s
  • docker-verification=91254004-3812-4bbf-8891-cfbcf6ab8a5a 300s
  • anthropic-domain-verification-79jhy9=snkFr9zlMHUQacKSA2jajDZWx 300s
  • 00DDd0000000Pzp=1TBDd000000000G 300s
  • jamf-site-verification=CRC3ONgiPtpCFGR2dfLdnA 300s
  • Dynatrace-site-verification=3394c98f-7ce9-4353-966e-df02b4a4dc42__7u76jred46uudm5c5a7i7b3qtl 300s
  • _x9ek4hy7f9iespeb3ausdy5k51nk09w 300s
  • onetrust-domain-verification=24f8a0b43242414ea6241e3bcaaf0bd9 300s
  • mongodb-site-verification=NeuPv2AWkw60t3gIozDEJKmVCJzcgcJE 300s
  • successfactors-site-verification=ZDg5YjM5ZTdhZWUyZTQ4OTFiMDliNGFlOTU5NTg4NmFiZjM2MjhjYzQ0MDY1YWI4ZjA4MTRlNDE0NjY0Y2I2MA== 300s
  • pardot873581=d73ef67a00be12aba3ae2dacb3ae7e004ee9accb6865c65efba4e3febadd1f13 300s
  • google-site-verification=L1RsT01hNCeXEROYDocswIT_W-54ykCHLwXWXUU2JBY 300s
  • _ag7xpv12j0j906kocotsikxn2o004pw 300s
  • 00D2D000000DUw7=1TBDf000000000L 300s
  • teamviewer-sso-verification=541c373bdcfa475a9a20157c4a29a252 300s
  • _3urx009ue0xyc8bnrmpy1hsx1g91l5u 300s
  • liveramp-site-verification=WyJKj0cYakBDln0jpkh-rsI3f6OEP3Nt4cETnJ3P0z0 300s
  • mirage-security-domain-verification-ccjev2=5to7kqsikJKS99eP7I5B9FWyf 300s
  • _lkq6lzgucpf6cyvm5i6x0qyxyuw0thh 300s

SOA Registros SOA

  • lf-dns01.grainger.com 1200s

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