Httpfy

DNS Report for ceair.com

Date Generated: 2024-09-14 03:45:55

Nameservers

Nameserver Count - OK

Nameserver Queries

  • vip3.alidns.com
    • Status: Responded
    • IP(s): 101.230.234.5, 115.223.7.10
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • vip4.alidns.com
    • Status: Responded
    • IP(s): 101.230.234.5, 115.223.7.10
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns3.ceair.com
    • Status: Responded
    • IP(s): 115.223.7.10
    • TTL: 600 seconds
    • Recursive Queries: Error checking recursive queries: The DNS operation timed out.
    • TCP Connectivity: TCP connection failed: The DNS operation timed out.
  • ltdns.ceair.com
    • Status: Responded
    • IP(s): 115.223.7.10
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

vip3.alidns.com
  • Serial: 2024082911
  • Refresh: 3600
  • Retry: 1200
  • Expire: 86400
  • Minimum TTL: 600
vip4.alidns.com
  • Serial: 2024083011
  • Refresh: 3600
  • Retry: 1200
  • Expire: 86400
  • Minimum TTL: 600
ns3.ceair.com

Error: The DNS operation timed out after 5.4013512134552 seconds

ltdns.ceair.com
  • Serial: 20063594
  • Refresh: 3600
  • Retry: 3600
  • Expire: 1296000
  • Minimum TTL: 600

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

MX Records

vip3.alidns.com
vip4.alidns.com
ns3.ceair.com

Error: The DNS operation timed out after 5.402348756790161 seconds

ltdns.ceair.com

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

  • 172.59.248.220.in-addr.arpa -> 220-248-59-172.sh.cncnet.net
  • 172.234.230.101.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 172.234.230.101.in-addr.arpa.

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 ip4:101.230.234.46 ip4:220.248.59.46 ip4:218.1.115.14 ip4:218.80.232.37 ip4:35.166.196.26 ip4:101.230.234.151 ip4:101.230.234.152 ip4:220.248.59.151 ip4:220.248.59.152 ip4:117.131.80.151 ip4:117.131.80.152 ip4:117.131.80.46 -all
  • SPF Syntax: Passed
  • Deprecated Elements: Passed
  • IP Addresses: 101.230.234.46, 220.248.59.46, 218.1.115.14, 218.80.232.37, 35.166.196.26, 101.230.234.151, 101.230.234.152, 220.248.59.151, 220.248.59.152, 117.131.80.151, 117.131.80.152, 117.131.80.46
  • Includes:
  • DNS Lookups: 1
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: -all

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