Httpfy

DNS Report for telegram.org

Date Generated: 2024-07-27 04:48:28

Nameservers

  • ns-cloud-b3.googledomains.com
    • IPv4: 216.239.36.107
    • IPv6: 2001:4860:4802:36::6b
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-cloud-b4.googledomains.com
    • IPv4: 216.239.38.107
    • IPv6: 2001:4860:4802:38::6b
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-cloud-b1.googledomains.com
    • IPv4: 216.239.32.107
    • IPv6: 2001:4860:4802:32::6b
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-cloud-b2.googledomains.com
    • IPv4: 216.239.34.107
    • IPv6: 2001:4860:4802:34::6b
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns-cloud-b3.googledomains.com
    • Status: Responded
    • IP(s): 149.154.167.99
    • TTL: 700 seconds
    • Recursive Queries: Unclear (Response code: NOERROR)
    • TCP Connectivity: Allows TCP connections
  • ns-cloud-b4.googledomains.com
    • Status: Responded
    • IP(s): 149.154.167.99
    • TTL: 700 seconds
    • Recursive Queries: Unclear (Response code: NOERROR)
    • TCP Connectivity: Allows TCP connections
  • ns-cloud-b1.googledomains.com
    • Status: Responded
    • IP(s): 149.154.167.99
    • TTL: 700 seconds
    • Recursive Queries: Unclear (Response code: NOERROR)
    • TCP Connectivity: Allows TCP connections
  • ns-cloud-b2.googledomains.com
    • Status: Responded
    • IP(s): 149.154.167.99
    • TTL: 700 seconds
    • Recursive Queries: Unclear (Response code: NOERROR)
    • TCP Connectivity: Allows TCP connections

SOA Records

ns-cloud-b3.googledomains.com
  • Serial: 2017053111
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 600
ns-cloud-b4.googledomains.com
  • Serial: 2017053111
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 600
ns-cloud-b1.googledomains.com
  • Serial: 2017053111
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 600
ns-cloud-b2.googledomains.com
  • Serial: 2017053111
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 600

Serial: 2017053111 - OK

REFRESH: 28800 - OK

RETRY: 7200 - OK

EXPIRE: 604800 - OK

MINIMUM TTL: 600 - Note: Outside recommended range (1-3 hours)

MX Records

ns-cloud-b3.googledomains.com
ns-cloud-b4.googledomains.com
ns-cloud-b1.googledomains.com
ns-cloud-b2.googledomains.com

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

  • 10.64.161.95.in-addr.arpa -> mx10.telegram.org
  • 16.64.161.95.in-addr.arpa -> mx101.telegram.org
  • 2.64.161.95.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 2.64.161.95.in-addr.arpa.

PTR Records - OK

  • Signed: No
  • Validation: Failed
  • DNSKEY Records: None
  • DS Records in parent zone: None
  • DS at Parent: None

DNSSEC - Note: Domain is not signed with DNSSEC

Error: No DNSSEC records found

SPF (Sender Policy Framework)

SPF Record Published: Passed

Multiple SPF Records: Passed

SPF Record 1:
  • Record: v=spf1 ip4:95.161.64.0/28 ip4:95.161.64.16/32 ip4:149.154.160.0/20 -all
  • SPF Syntax: Passed
  • Deprecated Elements: Passed
  • IP Addresses: 95.161.64.0/28, 95.161.64.16/32, 149.154.160.0/20
  • Includes:
  • DNS Lookups: 1
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: -all

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: mail
  • Selector 'mail':
    Record: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/GAy6qOB0bIXPmx1q9XCtDAf1phhIXFK2Xy8fQqMxasdJNQ81N5UxNEdtu8LR9055pxQdPtnhw0mfknqbPw9CVCzSc2X9kuTZbrVJ26neA5b+IJTo3C2W59cXs49wJFKKfqCMA/b8TnJIQZBgzZ0209rZriVtabEIcUzeo44tUwIDAQAB
  • Valid Syntax: Yes

DMARC

  • Record: v=DMARC1; p=reject; aspf=r; sp=reject; rua=mailto:[email protected]
  • Syntax: Valid
  • Policy: reject
  • Subdomain Policy: reject
  • RUA (Aggregate Reports): mailto:[email protected]
  • SPF Alignment (aspf): Relaxed
DMARC External Validation:
  • All external domains in your DMARC record are giving permission to send them DMARC reports.
Check DNS for Another Domain

Use our DNS Checker to analyze DNS records for any domain.

Go to DNS Checker