DNS records for telegram.me

Findings

[INFO] An SPF record is published but no MX records are present. This is normal for send-only domains but worth confirming if you expect to receive mail.

A records

[
  {
    "type": "A",
    "value": "149.154.167.99"
  }
]

AAAA records

[
  {
    "type": "AAAA",
    "value": "2001:67c:4e8:f004::9"
  }
]

NS records

[
  {
    "type": "NS",
    "value": "ns-cloud-d2.googledomains.com"
  },
  {
    "type": "NS",
    "value": "ns-cloud-d4.googledomains.com"
  },
  {
    "type": "NS",
    "value": "ns-cloud-d1.googledomains.com"
  },
  {
    "type": "NS",
    "value": "ns-cloud-d3.googledomains.com"
  }
]

TXT records

[
  {
    "type": "TXT",
    "entries": [
      "v=spf1 -all"
    ]
  }
]

SOA records

[
  {
    "type": "SOA",
    "nsname": "ns-cloud-d1.googledomains.com",
    "hostmaster": "dns.jomax.net.telegram.me",
    "serial": 2017053100,
    "refresh": 28800,
    "retry": 7200,
    "expire": 604800,
    "minttl": 600
  }
]

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 telegram.me.

Related tools: DNS Lookup · SPF Checker · DMARC Lookup