☰

bill.com

Endereço IP 44.238.33.13
DNS gerenciado por Amazon Route 53
E-mail Configurado
Registros 72

O domínio bill.com responde no endereço IP 44.238.33.13. O DNS do domínio é gerenciado por Amazon Route 53, que define para onde aponta cada subdomínio. O e-mail de bill.com passa por 1 servidores; o de maior prioridade é prodstarmail.prod.a.bill.com. Também publica 64 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

  • _jr0qurgcmsahqxmedykhw1x1w5k8cv5 1800s
  • _tgd4p6xtwpd456qg0cj7z84ef4b4643 1800s
  • _gtdudq3paeauwaiop852dho5rj1ysp4 1800s
  • _qh0vf1901pxy2oyt7nt7xvay7onvxaq 1800s
  • 5upfs4mjnd9p0ms167aek74aa3 1800s
  • _am1dnmww6intbqyhxrgwulxd2ybqy65 1800s
  • _guhn4i28k2cmzqwz2fojtkpa9f8xoh5 1800s
  • 00d4x0000017x4deau 1800s
  • _7omf62hmooufyx3kbnrj6y0ltxevyvr 1800s
  • vatmuro94mp1eit8q3njubgjcb 1800s
  • ca3-45b66649477f4e9cb9eb7d80e3c2c280 1800s
  • _dbr0oj333r0mqljf0hq6k6rc0gvobik 1800s
  • _kam0g0f778auzrkr6a2019x1bhil2cv 1800s
  • _jhb17jdcntvn6d8b3c583sjp7py36ir 1800s
  • adobe-idp-site-verification=2958172ee89b82a1dc713680c4e7a9c2720fe0550a651acb80a7bf12caf49205 1800s
  • _wq94msu5tubw6qfcl5yna8tvwzpzsa6 1800s
  • _blq2en6rujpmpvnr7gmq9mauc6mmpmm 1800s
  • k70an3f95eqe3k3lukt9lhgl8f 1800s
  • _cfa36n8r7ttrpkxahz8zqz2r8en4txt 1800s
  • _awzse8zd0pbbdb5d3f7c4mw6ixugx0r 1800s
  • _26qc6sut4ijvxxipa6lf3rlrzt8x6je 1800s
  • postman-domain-verification=4d1b31cde822949e47f87d3cb01938d4eda4c1c302807e7565433f0bddcb8af1fa8cc335c335521e33d1ce81b38fe58b0919f90db36eb5cd2fff50915c11d985 1800s
  • _i0heg3rrqvaw20nts3lwgpoo69t0z5n 1800s
  • n03tpa9afmgp6966e2rrq8i11k 1800s
  • _0w9jshohcm0uty73ynbkkndx6sms3mg 1800s
  • _5ek19tmbxmulop9f5yqmuuret22vc1q 1800s
  • _tv6id95mt2hhoh58gfqiq4wf9elu8mm 1800s
  • _x1o6aq3moz2qyynropmakzf2sue09eb 1800s
  • v=spf1 ip4:66.46.182.73 include:_spf.bill.com -all 1800s
  • google-site-verification=xz0sIfF3xTQhJBYPkeAXU-Js8jf4CHd6JcCnqYZFa8A 1800s
  • _7rk8zslqr7nimrizvctdewfvjvquces 1800s
  • rnv6n8k6ol6n1lg04qctiq2tso 1800s
  • dbsdj0sfda9b4gha3e0lskaufp 1800s
  • _toz90xj26xdsfa50d8lrilts8trj18h 1800s
  • _ugck6eircvdr9vgsmh7h5zp3fxs1xmk 1800s
  • jc1iajl972hv8cr0sqnur81fsp 1800s
  • f1gjka1kt5j693a142vs16bj9v 1800s
  • google-site-verification=rByWotBaOKhr6FCGPa26kSIDQathyiNyrLzpI09AgC4 1800s
  • _334nro53km79bizysbbkx9rh6m2gtuq 1800s
  • _cv5owl6mzjhod6hrsxctlmp4917ebfk 1800s
  • _aadb3al7gnbhjmc8gh6jl9bhioxh3oi 1800s
  • _si9l15a7qwna0ubpler69dsmxrjo6dl 1800s
  • p9dmi01qbqh1i07rg871n3bm81 1800s
  • _8z57lzlyctxha35e2rah7zfjpbqfj6h 1800s
  • _1tllkjwy6zpg912d2jzkbrj0i5cfxpk 1800s
  • 344rt98at1epk3p3n5iibjpqlh 1800s
  • _5xr6c02py69eyji75205t8raax86kcx 1800s
  • _x2fy3oj3gql7ulxogd8z9b5dlwi73od 1800s
  • _3xpl09vems5t6x0wi6f4gl2o8y7rr77 1800s
  • _dg25swqykxpyeofr73cxicoaepv4ass 1800s
  • _be3efmhcbu3rqychxlhz3dhnl9x33r7 1800s
  • eq5t6vklhroevl79pdvlqvg9dc 1800s
  • _tof2s0thvaue1g990xqt2g3otoem1kl 1800s
  • ps-cd-verification=872e3a6f-ab2e-41e3-92c2-d3689cef0403 1800s
  • google-site-verification=eqx9ag-bieP00I1OgVVdX4Q3R7-yfpj8Koo9-n9576k 1800s
  • google-site-verification=zXWDbKpIo5JUV2PVfxMSpiMH4nU2G09ex0EbUJJ6jg4 1800s
  • _v8dv9uj3mwdsmuhuozzztkjy0vxydd2 1800s
  • status-page-domain-verification=5x7xw7msxfgb 1800s
  • _5k6epr6i8z9lbpgjqmt2lf1vm7ghecc 1800s
  • o5o9bv4i9b08jehll4bua35nh8 1800s
  • _0nxbzkhla31uhi13par1ynlquoeobpw 1800s
  • _jxnk66cdry5dd5s087mh6c9kgmzpuz6 1800s
  • _62qdxi3aata0ij9ubhykkai7yn1d52e 1800s
  • _09y9s2h5ktsesj2d1rfjpphg77hith7 1800s

SOA Registros SOA

  • ns-1903.awsdns-45.co.uk 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á 3 horas.