inquirer.net
The domain inquirer.net answers at IP address 172.66.175.5. The domain DNS is managed by Cloudflare, which decides where each subdomain points. Mail for inquirer.net goes through 5 servers; the highest priority one is aspmx.l.google.com. It also publishes 13 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 172.66.175.5 300s
- 104.20.44.25 300s
AAAA AAAA records
MX MX records
- 1 aspmx.l.google.com 300s
- 5 alt2.aspmx.l.google.com 300s
- 5 alt1.aspmx.l.google.com 300s
- 10 alt4.aspmx.l.google.com 300s
- 10 alt3.aspmx.l.google.com 300s
NS NS records
- dawn.ns.cloudflare.com 21600s
- jay.ns.cloudflare.com 21600s
TXT TXT records
- sendinblue-code:be7642cc714e793a1e2e016116c33006 300s
- v=spf1 a mx include:_spf.elasticemail.com include:_spf.google.com include:20818607.spf02.hubspotemail.net include:spf.sendinblue.com ~all 300s
- facebook-domain-verification=xbz352h1e2ui4gbzp0k47la9v6vx2m 300s
- google-site-verification=2Occsvh7XtuhFMN_uNnl3XaL7Lm2a1hpuPbVKrhWrBk 300s
- clickfunnels-domain-verification=vBBpbK 300s
- google-site-verification=4SuYiV92RkTRIUQmCD21iPZvs20hHGmAlOa_WcTXWpo 300s
- google-site-verification=iclsJL576k2YzKuw4vqKeesL9H1KkYks62rB5C4mU3k 300s
- google-site-verification=fA5pUhQAXZRg_iHYlMI9tZOkYEsfU2Gg_HYwik46WvU 300s
- apple-domain-verification=ga2nyznDCrc5yErR 300s
- google-site-verification=olsaOqN7LTKOfvXL0gliBCSZrag5d2znH37_1EWkHrk 300s
- google-site-verification=-Y_ycsrXo28eAzxOxnDhNtZJ_UB7VZ_28qp6s8nXdxM 300s
- tollbit-domain-verification=ccafbec4ef56ec376e416353669455a0eba4c8bb00651a9aa1a3dcd24078b20f 300s
- have-i-been-pwned-verification=dweb_2b3gv0ag8gq8y8apn4ztm4sm 300s
SOA SOA records
- dawn.ns.cloudflare.com 1800s
What each record means
- A and AAAA: the server IP address, in IPv4 and IPv6.
- MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
- NS: the name servers, which have the final say over the domain DNS.
- TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
- TTL: how many seconds the record may be cached before asking again.
Checked 6 hours ago.