Httpfy

DNS Report for anz.com

Date Generated: 2024-08-20 15:13:42
Check Another Domain

Nameservers

  • a9-67.akam.net
    • IPv4: 184.85.248.67
    • IPv6: 2a02:26f0:117::43
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • a28-67.akam.net
    • IPv4: 95.100.173.67
    • IPv6: 2600:1480:d800::43
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • a7-66.akam.net
    • IPv4: 23.61.199.66
    • IPv6: 2600:1406:32::42
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • a1-206.akam.net
    • IPv4: 193.108.91.206
    • IPv6: 2600:1401:2::ce
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • a16-67.akam.net
    • IPv4: 23.211.132.67
    • IPv6: 2600:1406:1b::43
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • a8-67.akam.net
    • IPv4: 2.16.40.67
    • IPv6: 2600:1403:a::43
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • a9-67.akam.net
    • Status: Responded
    • IP(s): 45.60.124.46, 45.60.126.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • a28-67.akam.net
    • Status: Responded
    • IP(s): 45.60.126.46, 45.60.124.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • a7-66.akam.net
    • Status: Responded
    • IP(s): 45.60.126.46, 45.60.124.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • a1-206.akam.net
    • Status: Responded
    • IP(s): 45.60.126.46, 45.60.124.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • a16-67.akam.net
    • Status: Responded
    • IP(s): 45.60.124.46, 45.60.126.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • a8-67.akam.net
    • Status: Responded
    • IP(s): 45.60.124.46, 45.60.126.46
    • TTL: 10800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

SOA Records

a9-67.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600
a28-67.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600
a7-66.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600
a1-206.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600
a16-67.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600
a8-67.akam.net
  • Serial: 2009037706
  • Refresh: 3600
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 3600

Serial: 2009037706 - OK

REFRESH: 3600 - OK

RETRY: 3600 - OK

EXPIRE: 604800 - OK

MINIMUM TTL: 3600 - OK

MX Records

a9-67.akam.net
a28-67.akam.net
a7-66.akam.net
a1-206.akam.net
a16-67.akam.net
a8-67.akam.net

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 43.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 45.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 43.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 45.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 43.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 126.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 125.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 45.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 44.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 124.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 126.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 124.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 126.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 43.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 125.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 45.93.93.3.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 124.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com
  • 126.36.223.34.in-addr.arpa -> mx.us.email.fireeyecloud.com

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: Passed

Multiple SPF Records: Passed

SPF Record 1:
  • Record: v=spf1 ip4:64.106.214.50 ip4:103.19.144.26 ip4:68.233.76.14 ip4:103.19.194.158 ip4:149.72.170.64 ip4:203.18.160.203 ip4:103.3.196.47 ip4:203.32.185.199 ip4:203.32.185.77 include:_spf.fireeyecloud.com include:spfa.anz.com include:stspg-customer.com -all
  • SPF Syntax: Passed
  • Deprecated Elements: Passed
  • IP Addresses: 64.106.214.50, 103.19.144.26, 68.233.76.14, 103.19.194.158, 149.72.170.64, 203.18.160.203, 103.3.196.47, 203.32.185.199, 203.32.185.77
  • Includes: _spf.fireeyecloud.com, spfa.anz.com, stspg-customer.com
  • DNS Lookups: 6
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: -all

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: selector1
  • Selector 'selector1':
    Record: v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDCC90Bl0/g8KmDzYnVMvhMYc1zA5UWcyf8T9KhJNoV/w5uVqXbCS2TK2/rPE2i0eZXwgg5wJ8LdGo1LTdHTVodfIYbEycha4RbUh5XCHyUTD3IYafNguz/Yf8A4rpu4odi5yixfHGOFnjEa/vY/U0xBnGimqlWiseXWB59+0KBYQIDAQAB;
  • 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

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

Copyright © 2024 HTTPfy Terms & Conditions - Privacy Policy