DNS records for substack.com
A records
[
{
"type": "A",
"value": "104.18.37.200"
},
{
"type": "A",
"value": "172.64.150.56"
}
]AAAA records
[
{
"type": "AAAA",
"value": "2606:4700:4400::ac40:9638"
},
{
"type": "AAAA",
"value": "2606:4700:440b::6812:25c8"
}
]MX records
[
{
"type": "MX",
"exchange": "mxa.mailgun.org",
"priority": 10
},
{
"type": "MX",
"exchange": "mxb.mailgun.org",
"priority": 10
}
]NS records
[
{
"type": "NS",
"value": "lee.ns.cloudflare.com"
},
{
"type": "NS",
"value": "ali.ns.cloudflare.com"
}
]TXT records
[
{
"type": "TXT",
"entries": [
"google-site-verification=FfNIQIxsRHpj3Y7E_d3N6GFqGgWDZ-sfYojqCilwtqE"
]
},
{
"type": "TXT",
"entries": [
"google-site-verification=DAkdykID6WqQM6tT7IfSu9_uB7-qIdB039MA_C3T3eA"
]
},
{
"type": "TXT",
"entries": [
"tiktok-developers-site-verification=7PgqCAJ52ILLOqf2KELd8uaRfJpuzaLQ"
]
},
{
"type": "TXT",
"entries": [
"google-site-verification=4V_X38Yf0J4VJcWFwtG38bOS1nkOWeIWJhticlMgNQE"
]
},
{
"type": "TXT",
"entries": [
"tiktok-developers-site-verification=A9XRSo8lWy5CPFJ0bqI04KCpUZGAAq7p"
]
},
{
"type": "TXT",
"entries": [
"v=spf1 include:_spf.google.com include:mailgun.org include:mail.zendesk.com ~all"
]
},
{
"type": "TXT",
"entries": [
"google-site-verification=vQEKLOUDfKNOQAv9W3EUMiRD6e5ibAEPhc2yCzP7big"
]
},
{
"type": "TXT",
"entries": [
"facebook-domain-verification=8vbxp2ntmkudc6is3h5r840c9fwo7f"
]
},
{
"type": "TXT",
"entries": [
"google-site-verification=SXEl7_p4SBszcanSWwVc_3-RFky80c0-94janbeeWI4"
]
}
]SOA records
[
{
"type": "SOA",
"nsname": "ali.ns.cloudflare.com",
"hostmaster": "dns.cloudflare.com",
"serial": 2399990522,
"refresh": 10000,
"retry": 2400,
"expire": 604800,
"minttl": 1800
}
]What does this mean?
These records are pulled live from authoritative DNS at request time and re-validated daily. Use them to debug routing, deliverability, and TLS issues for substack.com.
Related tools: DNS Lookup · SPF Checker · DMARC Lookup