Httpfy

DNS Report for 300hu.com

Date Generated: 2024-08-19 16:52:52
Check Another Domain

Nameservers

  • ns4.jd.com
    • IPv4: 106.39.177.32
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1.jd.com
    • IPv4: 111.13.28.10
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns3.jd.com
    • IPv4: 120.52.149.254
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns5.jd.com
    • IPv4: 120.52.149.254
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns2.jd.com
    • IPv4: 111.206.226.10
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns4.jd.com
    • Status: Responded
    • IP(s): 36.110.180.149
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns1.jd.com
    • Status: Responded
    • IP(s): 36.110.180.149
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns3.jd.com
    • Status: Responded
    • IP(s): 36.110.180.149
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns5.jd.com
    • Status: Responded
    • IP(s): 36.110.180.149
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns2.jd.com
    • Status: Responded
    • IP(s): 36.110.180.149
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns4.jd.com
  • Serial: 2018042499
  • Refresh: 10800
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 38400
ns1.jd.com
  • Serial: 2018042499
  • Refresh: 10800
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 38400
ns3.jd.com
  • Serial: 2018042499
  • Refresh: 10800
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 38400
ns5.jd.com
  • Serial: 2018042499
  • Refresh: 10800
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 38400
ns2.jd.com
  • Serial: 2018042499
  • Refresh: 10800
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 38400

Serial: 2018042499 - OK

REFRESH: 10800 - OK

RETRY: 3600 - OK

EXPIRE: 604800 - OK

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

MX Records

ns4.jd.com
ns1.jd.com
ns3.jd.com
ns5.jd.com
ns2.jd.com

MX Record Consistency - OK

MX Record Count - Warning: Only one MX record

Reverse MX A records (PTR)

  • 35.200.124.111.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 35.200.124.111.in-addr.arpa.

PTR Records - OK

DNSSEC

DNSSEC Inspector
  • 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: Failed

Multiple SPF Records: Passed

Errors:
  • No SPF record found

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: No
Warnings:
  • No DKIM records found for common selectors
Errors:
  • Error checking DKIM for selector 'default': The DNS operation timed out after 5.461258888244629 seconds
  • Error checking DKIM for selector 'key1': The DNS operation timed out after 5.468350887298584 seconds
  • Error checking DKIM for selector 'mxvault': The DNS operation timed out after 5.564936399459839 seconds
  • Error checking DKIM for selector 'yahoo': The DNS operation timed out after 5.463165283203125 seconds
  • Error checking DKIM for selector 'pm': The DNS operation timed out after 5.41991400718689 seconds
  • Error checking DKIM for selector 'proxy1': All nameservers failed to answer the query proxy1._domainkey.300hu.com. IN TXT: Server 172.20.0.10 UDP port 53 answered The DNS operation timed out.; Server 172.20.0.10 UDP port 53 answered The DNS operation timed out.; Server 172.20.0.10 UDP port 53 answered SERVFAIL
  • Error checking DKIM for selector 'proxy2': The DNS operation timed out after 5.527140855789185 seconds
  • Error checking DKIM for selector 'ses': The DNS operation timed out after 5.413740873336792 seconds
  • Error checking DKIM for selector 'click': The DNS operation timed out after 5.46758770942688 seconds
  • Error checking DKIM for selector 'click1': The DNS operation timed out after 5.431706190109253 seconds
  • Error checking DKIM for selector 'goog': The DNS operation timed out after 5.450317621231079 seconds
  • Error checking DKIM for selector '2020': The DNS operation timed out after 5.413777589797974 seconds
  • Error checking DKIM for selector '2022': The DNS operation timed out after 5.441328763961792 seconds
  • Error checking DKIM for selector '2023': The DNS operation timed out after 5.403870344161987 seconds
  • Error checking DKIM for selector '20160929': The DNS operation timed out after 5.471368312835693 seconds
  • Error checking DKIM for selector 'z2': The DNS operation timed out after 5.404883623123169 seconds
  • Error checking DKIM for selector 'z3': The DNS operation timed out after 5.484875917434692 seconds
  • Error checking DKIM for selector 'jan2014': The DNS operation timed out after 5.419560670852661 seconds
  • Error checking DKIM for selector 'feb2014': The DNS operation timed out after 5.421370983123779 seconds
  • Error checking DKIM for selector 'mar2014': The DNS operation timed out after 5.526255369186401 seconds
  • Error checking DKIM for selector 'may2014': The DNS operation timed out after 5.40752387046814 seconds
  • Error checking DKIM for selector 'jun2014': The DNS operation timed out after 5.417159080505371 seconds
  • Error checking DKIM for selector 'jul2014': The DNS operation timed out after 5.445221662521362 seconds
  • Error checking DKIM for selector 'feb2015': The DNS operation timed out after 5.411432504653931 seconds
  • Error checking DKIM for selector 'apr2015': The DNS operation timed out after 5.42009162902832 seconds
  • Error checking DKIM for selector 'oct2015': The DNS operation timed out after 5.421733856201172 seconds
  • Error checking DKIM for selector 'dec2015': The DNS operation timed out after 5.441627264022827 seconds
  • Error checking DKIM for selector 'v2': The DNS operation timed out after 5.427762031555176 seconds
  • Error checking DKIM for selector 'smtpapi': The DNS operation timed out after 5.41646933555603 seconds
  • Error checking DKIM for selector 'services': The DNS operation timed out after 5.412766695022583 seconds

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:
  • Error checking DMARC: The DNS operation timed out after 5.4456071853637695 seconds
Check DNS for Another Domain

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

Go to DNS Checker

Empower Your Network, Enhance Your DevOps: The Ultimate Online Tools Hub

Copyright © 2024 HTTPfy Terms & Conditions - Privacy Policy