Httpfy

DNS Report for adrta.com

Date Generated: 2024-07-27 15:19:27
Check Another Domain

Nameservers

  • ns-1157.awsdns-16.org
    • IPv4: 205.251.196.133
    • IPv6: 2600:9000:5304:8500::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-1793.awsdns-32.co.uk
    • IPv4: 205.251.199.1
    • IPv6: 2600:9000:5307:100::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-433.awsdns-54.com
    • IPv4: 205.251.193.177
    • IPv6: 2600:9000:5301:b100::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-615.awsdns-12.net
    • IPv4: 205.251.194.103
    • IPv6: 2600:9000:5302:6700::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns-1157.awsdns-16.org
    • Status: Responded
    • IP(s): 44.215.148.1, 44.218.191.29, 35.173.102.218, 3.227.213.57, 52.20.63.118, 44.217.0.34, 18.232.224.205, 50.16.91.228
    • TTL: 60 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns-1793.awsdns-32.co.uk
    • Status: Responded
    • IP(s): 18.232.224.205, 52.20.63.118, 44.215.148.1, 3.227.213.57, 50.16.91.228, 44.218.191.29, 54.91.247.171, 44.217.0.34
    • TTL: 60 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-433.awsdns-54.com
    • Status: Responded
    • IP(s): 44.196.140.13, 3.227.213.57, 18.232.224.205, 52.20.63.118, 50.16.91.228, 54.91.247.171, 44.218.191.29, 34.194.174.188
    • TTL: 60 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-615.awsdns-12.net
    • Status: Responded
    • IP(s): 54.91.247.171, 44.217.0.34, 44.196.140.13, 3.94.222.3, 44.218.191.29, 34.194.174.188, 54.209.58.130, 18.232.224.205
    • TTL: 60 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns-1157.awsdns-16.org
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-1793.awsdns-32.co.uk
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-433.awsdns-54.com
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-615.awsdns-12.net
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400

Serial: 1 - OK

REFRESH: 7200 - OK

RETRY: 900 - OK

EXPIRE: 1209600 - OK

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

MX Records

ns-1157.awsdns-16.org
ns-1793.awsdns-32.co.uk
ns-433.awsdns-54.com
ns-615.awsdns-12.net

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 93.5.153.54.in-addr.arpa -> ec2-54-153-5-93.us-west-1.compute.amazonaws.com
  • 27.184.233.64.in-addr.arpa -> wa-in-f27.1e100.net
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 26.16.251.142.in-addr.arpa -> bl-in-f26.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 27.184.233.64.in-addr.arpa -> wa-in-f27.1e100.net
  • 26.62.253.172.in-addr.arpa -> bc-in-f26.1e100.net
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.1e100.net

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

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:
  • DMARC record does not exist
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