Httpfy

DNS Report for reuters.com

Date Generated: 2024-08-16 17:13:23

Nameservers

  • ns-emea-1.thomsonreuters.net
    • IPv4: 155.46.156.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns-amers-1.thomsonreuters.net
    • IPv4: 155.46.165.133
    • IPv6: No IPv6 found
    • TTL (IPv4): 5 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns-amers-3.thomsonreuters.net
    • IPv4: 155.46.152.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 5 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns-emea-2.thomsonreuters.net
    • IPv4: 155.46.154.12
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns-emea-1.thomsonreuters.net
    • Status: Responded
    • IP(s): 155.46.172.255
    • TTL: 300 seconds
    • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
    • TCP Connectivity: TCP connection failed: The DNS operation timed out.
  • ns-amers-1.thomsonreuters.net
    • Status: Responded
    • IP(s): 155.46.172.255
    • TTL: 300 seconds
    • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
    • TCP Connectivity: TCP connection failed: The DNS operation timed out.
  • ns-amers-3.thomsonreuters.net
    • Status: Responded
    • IP(s): 155.46.172.255
    • TTL: 300 seconds
    • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
    • TCP Connectivity: TCP connection failed: The DNS operation timed out.
  • ns-emea-2.thomsonreuters.net
    • Status: Responded
    • IP(s): 155.46.172.255
    • TTL: 300 seconds
    • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
    • TCP Connectivity: TCP connection failed: The DNS operation timed out.

SOA Records

ns-emea-1.thomsonreuters.net
  • Serial: 2019113931
  • Refresh: 3600
  • Retry: 900
  • Expire: 2419200
  • Minimum TTL: 30
ns-amers-1.thomsonreuters.net
  • Serial: 2019113931
  • Refresh: 3600
  • Retry: 900
  • Expire: 2419200
  • Minimum TTL: 30
ns-amers-3.thomsonreuters.net
  • Serial: 2019113931
  • Refresh: 3600
  • Retry: 900
  • Expire: 2419200
  • Minimum TTL: 30
ns-emea-2.thomsonreuters.net
  • Serial: 2019113931
  • Refresh: 3600
  • Retry: 900
  • Expire: 2419200
  • Minimum TTL: 30

Serial: 2019113931 - OK

REFRESH: 3600 - OK

RETRY: 900 - OK

EXPIRE: 2419200 - OK

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

MX Records

ns-emea-1.thomsonreuters.net
ns-amers-1.thomsonreuters.net
ns-amers-3.thomsonreuters.net
ns-emea-2.thomsonreuters.net

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

  • 180.179.220.205.in-addr.arpa -> mx0b-00160c04.pphosted.com
  • 179.167.220.205.in-addr.arpa -> mx0a-00160c04.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: selector1
  • Selector 'selector1':
    Record: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwjnBe+Q6zdxEJmN3yzNPD+/2YrnV8vodhqIeHr1basHFnBBwMBV9S4uGz3oH12CGQzuz92AOhdMJ+RtPO+aDJEKpOtn3N7Thkq/iNy37/8bl7i4u1zHiih3mAltrMnJ4Z1YHl6+4Gja2Vs1YZYpdCAcAC0iqQg59wf0qnT7HcKwIDAQAB; n=1024,1450207371,1
  • Valid Syntax: Yes

DMARC

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