Httpfy

DNS Report for utorrent.li

Date Generated: 2024-09-03 16:45:52

Nameservers

  • ns2.utorrent.com
    • IPv4: 204.152.200.170
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1.utorrent.com
    • IPv4: 216.45.48.250
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • dns-04.bittorrent.com
    • IPv4: No IPv4 found
    • IPv6: No IPv6 found
    • TTL (IPv4): N/A seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns3.utorrent.com
    • IPv4: 204.152.200.186
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns2.utorrent.com
    • Status: Responded
    • IP(s): 67.215.233.130
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.utorrent.com
    • Status: Responded
    • IP(s): 67.215.233.130
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns3.utorrent.com
    • Status: Responded
    • IP(s): 67.215.233.130
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns2.utorrent.com
  • Serial: 2014043009
  • Refresh: 3600
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 300
ns1.utorrent.com
  • Serial: 2014043009
  • Refresh: 3600
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 300
ns3.utorrent.com
  • Serial: 2014043009
  • Refresh: 3600
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 300

Serial: 2014043009 - OK

REFRESH: 3600 - OK

RETRY: 900 - OK

EXPIRE: 1209600 - OK

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

MX Records

ns2.utorrent.com
ns1.utorrent.com
ns3.utorrent.com

MX Record Consistency - OK

MX Record Count - Warning: Only one MX record

Reverse MX A records (PTR)

  • 121.115.253.172.in-addr.arpa -> bg-in-f121.1e100.net

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 a mx include:gmail.com ip4:64.127.109.128/25 ip4:208.72.193.0/24 ip4:216.45.48.250 ip4:204.152.200.170 ip4:204.152.200.186 ~all
  • SPF Syntax: Failed
  • Deprecated Elements: Passed
  • IP Addresses: 64.127.109.128/25, 208.72.193.0/24, 216.45.48.250, 204.152.200.170, 204.152.200.186
  • Includes: gmail.com
  • DNS Lookups: 5
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all
Errors:
  • SPF record syntax is invalid

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: No
Warnings:
  • No DKIM records found for common selectors

DMARC

  • Record: None
  • Syntax: Invalid
  • Policy: None
  • RUA (Aggregate Reports):
DMARC External Validation:
  • All external domains in your DMARC record are giving permission to send them DMARC reports.
Errors:
  • DMARC record does not exist
Check DNS for Another Domain

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

Go to DNS Checker