Httpfy

DNS Report for bscedge.com

Date Generated: 2024-08-22 00:22:46

Nameservers

  • gnscom2.v.solocdn.cn
  • com1.solocdn.cn
  • com2.solocdn.cn
    • IPv4: 218.92.147.153
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • com3.solocdn.cn
    • IPv4: 120.226.156.155
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • gnscom1.v.solocdn.cn

Nameserver Count - OK

Nameserver Queries

  • gnscom2.v.solocdn.cn
    • Status: Responded
    • IP(s): 183.61.189.213
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • com1.solocdn.cn
    • Status: Responded
    • IP(s): 183.61.189.213
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • com2.solocdn.cn
    • Status: Responded
    • IP(s): 183.61.189.213
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • com3.solocdn.cn
    • Status: Responded
    • IP(s): 183.61.189.213
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • gnscom1.v.solocdn.cn
    • Status: Responded
    • IP(s): 183.61.189.213
    • TTL: 600 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

gnscom2.v.solocdn.cn
  • Serial: 0
  • Refresh: 86400
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 300
com1.solocdn.cn
  • Serial: 0
  • Refresh: 86400
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 300
com2.solocdn.cn
  • Serial: 0
  • Refresh: 86400
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 300
com3.solocdn.cn
  • Serial: 0
  • Refresh: 86400
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 300
gnscom1.v.solocdn.cn
  • Serial: 0
  • Refresh: 86400
  • Retry: 3600
  • Expire: 604800
  • Minimum TTL: 300

Serial: 0 - OK

REFRESH: 86400 - OK

RETRY: 3600 - OK

EXPIRE: 604800 - OK

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

MX Records

gnscom2.v.solocdn.cn

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

com1.solocdn.cn

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

com2.solocdn.cn

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

com3.solocdn.cn

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

gnscom1.v.solocdn.cn

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

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

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 (Sender Policy Framework)

SPF Record Published: Failed

Multiple SPF Records: Passed

Errors:
  • No TXT records 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