DNS Report for yeahmobi.com

• ns-1443.awsdns-52.org

  • IPv4: 205.251.197.163
  • IPv6: 2600:9000:5305:a300::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-1564.awsdns-03.co.uk

  • IPv4: 205.251.198.28
  • IPv6: 2600:9000:5306:1c00::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-245.awsdns-30.com

  • IPv4: 205.251.192.245
  • IPv6: 2600:9000:5300:f500::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

• ns-858.awsdns-43.net

  • IPv4: 205.251.195.90
  • IPv6: 2600:9000:5303:5a00::1
  • TTL (IPv4): 30 seconds
  • TTL (IPv6): 30 seconds
  • Recursive: N/A

Nameserver Count - OK

• ns-1443.awsdns-52.org

  • Status: Responded
  • IP(s): 8.222.193.139
  • TTL: 300 seconds
  • Recursive Queries: Unclear (Response code: NXDOMAIN)
  • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

• ns-1564.awsdns-03.co.uk

  • Status: Responded
  • IP(s): 8.222.193.139
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns-245.awsdns-30.com

  • Status: Responded
  • IP(s): 8.222.193.139
  • TTL: 300 seconds
  • Recursive Queries: Does not allow recursive queries
  • TCP Connectivity: TCP connection failed (Response code: REFUSED)

• ns-858.awsdns-43.net

  • Status: Responded
  • IP(s): 8.222.193.139
  • TTL: 300 seconds
  • Recursive Queries: Unclear (Response code: NXDOMAIN)
  • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

ns-1443.awsdns-52.org

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-1564.awsdns-03.co.uk

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-245.awsdns-30.com

• Serial: 1
• Refresh: 7200
• Retry: 900
• Expire: 1209600
• Minimum TTL: 86400

ns-858.awsdns-43.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)

ns-1443.awsdns-52.org

• 1 mx1.feishu.cn ( 54.221.254.138 )
• 5 mx2.feishu.cn ( 122.14.229.0 )
• 10 mx3.feishu.cn ( 122.14.229.0 )

ns-1564.awsdns-03.co.uk

• 1 mx1.feishu.cn ( 54.221.254.138 )
• 5 mx2.feishu.cn ( 220.243.190.1 )
• 10 mx3.feishu.cn ( 52.220.106.220 )

ns-245.awsdns-30.com

• 1 mx1.feishu.cn ( 54.221.254.138 )
• 5 mx2.feishu.cn ( 220.243.190.1 )
• 10 mx3.feishu.cn ( 52.220.106.220 )

ns-858.awsdns-43.net

• 1 mx1.feishu.cn ( 54.221.254.138 )
• 5 mx2.feishu.cn ( 122.14.229.0 )
• 10 mx3.feishu.cn ( 220.243.190.1 )

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

• 1.190.243.220.in-addr.arpa -> No PTR record found: The DNS operation timed out after 5.430005073547363 seconds
• 1.190.243.220.in-addr.arpa -> No PTR record found: All nameservers failed to answer the query 1.190.243.220.in-addr.arpa. IN PTR: Server 172.20.0.10 UDP port 53 answered SERVFAIL
• 0.229.14.122.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 0.229.14.122.in-addr.arpa.
• 0.229.14.122.in-addr.arpa -> No PTR record found: The DNS query name does not exist: 0.229.14.122.in-addr.arpa.
• 220.106.220.52.in-addr.arpa -> ec2-52-220-106-220.ap-southeast-1.compute.amazonaws.com
• 138.254.221.54.in-addr.arpa -> ec2-54-221-254-138.compute-1.amazonaws.com

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

Multiple SPF Records: Passed

SPF Record 1:

• Record: v=spf1 +include:_netblocks.m.feishu.cn ~all
• SPF Syntax: Passed
• Deprecated Elements: Passed
• IP Addresses:
• Includes: _netblocks.m.feishu.cn
• DNS Lookups: 2
• Void Lookups: Passed
• Escaping Chars: Not Present
• All Mechanism: ~all

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

• DMARC record does not exist