Httpfy

DNS Report for thehartford.com

Date Generated: 2024-09-02 17:38:48

Nameservers

  • ns1.thehartford.com
    • IPv4: 162.136.188.1
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • simns3.thehartford.com
    • IPv4: 162.136.190.3
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns4.thehartford.com
    • IPv4: 162.136.24.8
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • simns4.thehartford.com
    • IPv4: 162.136.190.4
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns2.thehartford.com
    • IPv4: 162.136.190.1
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • hfdns3.thehartford.com
    • IPv4: 162.136.188.3
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • hfdns4.thehartford.com
    • IPv4: 162.136.188.4
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns3.thehartford.com
    • IPv4: 162.136.23.8
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - Note: 8 nameservers (recommended: 2-7)

Nameserver Queries

  • ns1.thehartford.com
    • Status: Responded
    • IP(s): 162.136.188.192, 162.136.190.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • simns3.thehartford.com
    • Status: Responded
    • IP(s): 162.136.190.192, 162.136.188.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns4.thehartford.com
    • Status: Responded
    • IP(s): 162.136.190.192, 162.136.188.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • simns4.thehartford.com
    • Status: Responded
    • IP(s): 162.136.188.192, 162.136.190.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns2.thehartford.com
    • Status: Responded
    • IP(s): 162.136.188.192, 162.136.190.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • hfdns3.thehartford.com
    • Status: Responded
    • IP(s): 162.136.190.192, 162.136.188.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • hfdns4.thehartford.com
    • Status: Responded
    • IP(s): 162.136.190.192, 162.136.188.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns3.thehartford.com
    • Status: Responded
    • IP(s): 162.136.188.192, 162.136.190.192
    • TTL: 120 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

SOA Records

ns1.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
simns3.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
ns4.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
simns4.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
ns2.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
hfdns3.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
hfdns4.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120
ns3.thehartford.com
  • Serial: 2024083182
  • Refresh: 1800
  • Retry: 900
  • Expire: 604800
  • Minimum TTL: 120

Serial: 2024083182 - OK

REFRESH: 1800 - OK

RETRY: 900 - OK

EXPIRE: 604800 - OK

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

MX Records

ns1.thehartford.com
simns3.thehartford.com
ns4.thehartford.com
simns4.thehartford.com
ns2.thehartford.com
hfdns3.thehartford.com
hfdns4.thehartford.com
ns3.thehartford.com

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

  • 63.139.163.148.in-addr.arpa -> mx0b-001bde01.pphosted.com
  • 63.135.163.148.in-addr.arpa -> mx0a-001bde01.pphosted.com

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 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
  • SPF Syntax: Failed
  • Deprecated Elements: Passed
  • IP Addresses:
  • Includes: %{ir}.%{v}.%{d}.spf.has.pphosted.com
  • DNS Lookups: 3
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all
Errors:
  • SPF record syntax is invalid

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: mandrill
  • Selector 'mandrill':
    Record: v=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB
  • Valid Syntax: Yes

DMARC

DMARC External Validation:
  • Valid external domains: emaildefense.proofpoint.com, dmarc.everest.email, emaildefense.proofpoint.com, dmarc.everest.email
  • 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