DNS Report for highrevenuenetwork.com

• ns3.publicdnsservice.com

  • IPv4: 64.58.124.135
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns2.publicdnsservice.com

  • IPv4: 64.58.124.140
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns1.publicdnsservice.com

  • IPv4: 64.58.124.134
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

• ns4.publicdnsservice.com

  • IPv4: 64.58.124.129
  • IPv6: No IPv6 found
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): N/A seconds
  • Recursive: N/A

Nameserver Count - OK

• ns3.publicdnsservice.com

  • Status: Failed: The DNS operation timed out after 5.426154851913452 seconds
  • IP(s):
  • TTL: N/A seconds
  • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
  • TCP Connectivity: TCP connection failed: The DNS operation timed out.

• ns2.publicdnsservice.com

  • Status: Failed: The DNS operation timed out after 5.42465615272522 seconds
  • IP(s):
  • TTL: N/A seconds
  • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
  • TCP Connectivity: TCP connection failed: The DNS operation timed out.

• ns1.publicdnsservice.com

  • Status: Responded
  • IP(s): 192.243.61.227, 172.240.108.68, 192.243.61.225, 192.243.59.12, 192.243.59.13, 172.240.108.84, 172.240.127.234, 192.243.59.20, 172.240.253.132, 172.240.108.76
  • TTL: 600 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns4.publicdnsservice.com

  • Status: Responded
  • IP(s): 192.243.61.227, 192.243.59.12, 192.243.59.20, 172.240.108.84, 192.243.59.13, 172.240.127.234, 192.243.61.225, 172.240.253.132, 172.240.108.68, 172.240.108.76
  • TTL: 600 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

ns3.publicdnsservice.com

Error: The DNS operation timed out after 5.423328638076782 seconds

ns2.publicdnsservice.com

Error: The DNS operation timed out after 5.409059047698975 seconds

ns1.publicdnsservice.com

• Serial: 2024080904
• Refresh: 10800
• Retry: 3600
• Expire: 604800
• Minimum TTL: 3600

ns4.publicdnsservice.com

• Serial: 2024080904
• Refresh: 10800
• Retry: 3600
• Expire: 604800
• Minimum TTL: 3600

Serial - Warning: Inconsistent across nameservers

REFRESH - Warning: Inconsistent across nameservers

RETRY - Warning: Inconsistent across nameservers

EXPIRE - Warning: Inconsistent across nameservers

MINIMUM TTL - Warning: Inconsistent across nameservers

ns3.publicdnsservice.com

Error: The DNS operation timed out after 5.43623948097229 seconds

ns2.publicdnsservice.com

Error: The DNS operation timed out after 5.426946640014648 seconds

ns1.publicdnsservice.com

Error: The DNS response does not contain an answer to the question: highrevenuenetwork.com. IN MX

ns4.publicdnsservice.com

Error: The DNS response does not contain an answer to the question: highrevenuenetwork.com. IN MX

MX Record Consistency - OK

MX Record Count - OK

No PTR records data available.

• 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 Record Published: Failed

Multiple SPF Records: Passed

Errors:

• No TXT records found

• DKIM Records Found: No

Warnings:

• No DKIM records found for common selectors

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

• No DMARC record found