Check DNS, Urls + Redirects, Certificates and Content of your Website



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
27.07.2020 20:35:39


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
c3cdn.ml.youngame.com

Name Error
yes
1
0
www.c3cdn.ml.youngame.com

Name Error
yes
1
0
*.ml.youngame.com
A
Fatal: DNS Timeout
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.c3cdn.ml.youngame.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 46594, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.08.2020, 00:00:00 +, Signature-Inception: 21.07.2020, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.08.2020, 17:00:00 +, Signature-Inception: 27.07.2020, 16:00:00 +, KeyTag 46594, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 46594 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 24966, Flags 256



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 08.08.2020, 18:24:21 +, Signature-Inception: 24.07.2020, 18:19:21 +, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: youngame.com
youngame.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "d0enas44qgt3fo3pqgvk0h9d9k796bme" between the hashed NSEC3-owner "d0emgivuiq7sli8lasina1u1f0ebdvta" and the hashed NextOwner "d0eni464su380vdlo1vt1mi42g3e39er". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner d0emgivuiq7sli8lasina1u1f0ebdvta.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.08.2020, 05:40:24 +, Signature-Inception: 25.07.2020, 04:30:24 +, KeyTag 24966, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q1gin43n1arrc9osm6qpqr81h5m9a". So that domain name is the Closest Encloser of "youngame.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.08.2020, 04:41:01 +, Signature-Inception: 25.07.2020, 03:31:01 +, KeyTag 24966, Signer-Name: com



0 DNSKEY RR found




Zone: ml.youngame.com
ml.youngame.com
0 DS RR in the parent zone found

Zone: c3cdn.ml.youngame.com
c3cdn.ml.youngame.com
0 DS RR in the parent zone found

Zone: www.c3cdn.ml.youngame.com
www.c3cdn.ml.youngame.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.c3cdn.ml.youngame.com
  f1g1ns1.dnspod.net

c3cdn.ml.youngame.com
  f1g1ns1.dnspod.net

ml.youngame.com
  f1g1ns1.dnspod.net

youngame.com
T  f1g1ns1.dnspod.net
129.211.176.187
Haidian/Beijing/China (CN) - Shenzhen Tencent Computer Systems Company Limited


 
14.215.150.17
Guangzhou Shi/Guangdong/China (CN) - China Telecom (Group)


 
14.215.155.156
Guangzhou Shi/Guangdong/China (CN) - China Telecom (Group)


 
14.215.155.170
Guangzhou Shi/Guangdong/China (CN) - China Telecom (Group)


 
183.192.164.117
Shanghai/China (CN) - China Mobile communications corporation


 
58.247.212.36
Shanghai/China (CN) - CNC Group CHINA169 Shanghai Province Network


 
61.151.180.44
Shanghai/China (CN) - China Telecom (Group)


  f1g1ns2.dnspod.net
101.226.220.16
Shanghai/China (CN) - China Telecom (Group)


 
129.211.176.224
Haidian/Beijing/China (CN) - Shenzhen Tencent Computer Systems Company Limited


 
14.215.155.203
Guangzhou Shi/Guangdong/China (CN) - China Telecom (Group)


 
162.14.24.230
Ho Chi Minh City/Ho Chi Minh/Vietnam (VN) - Shenzhen Tencent Computer Systems Company Limited


 
183.192.201.90
Guangzhou/Guangdong/China (CN) - China Mobile communications corporation


 
58.247.212.119
Shanghai/China (CN) - CNC Group CHINA169 Shanghai Province Network


 
58.247.212.48
Shanghai/China (CN) - CNC Group CHINA169 Shanghai Province Network

com
  a.gtld-servers.net


  b.gtld-servers.net


  c.gtld-servers.net


  d.gtld-servers.net


  e.gtld-servers.net


  f.gtld-servers.net


  g.gtld-servers.net


  h.gtld-servers.net


  i.gtld-servers.net


  j.gtld-servers.net


  k.gtld-servers.net


  l.gtld-servers.net


  m.gtld-servers.net


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1595874905
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1595874920
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:youngame.com
Zone-Name:youngame.com
Primary:f1g1ns1.dnspod.net
Mail:freednsadmin.dnspod.com
Serial:1588163737
Refresh:3600
Retry:180
Expire:1209600
TTL:180
num Entries:14


Domain:ml.youngame.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:c3cdn.ml.youngame.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.c3cdn.ml.youngame.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "c3cdn.ml.youngame.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 50272 (complete: 126568)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AInfo:: 9 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 9 Queries complete, 5 with IPv6, 4 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Ok (4 - 8):: An average of 4.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net, 2 Name Servers included in Delegation: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net, 2 Name Servers included in 1 Zone definitions: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net, 1 Name Servers listed in SOA.Primary: f1g1ns1.dnspod.net.
AGood: Only one SOA.Primary Name Server found.: f1g1ns1.dnspod.net.
AGood: SOA.Primary Name Server included in the delegation set.: f1g1ns1.dnspod.net.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 14 Name Servers, 7 different subnets (first Byte): 101., 129., 14., 162., 183., 58., 61., 7 different subnets (first two Bytes): 101.226., 129.211., 14.215., 162.14., 183.192., 58.247., 61.151., 9 different subnets (first three Bytes): 101.226.220., 129.211.176., 14.215.150., 14.215.155., 162.14.24., 183.192.164., 183.192.201., 58.247.212., 61.151.180.
AGood: Name Server IPv4-addresses from different subnet found:
XNameserver Timeout checking EDNS512: f1g1ns1.dnspod.net / 129.211.176.187
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 135720 milliseconds, 135.720 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: f1g1ns1.dnspod.net, f1g1ns2.dnspod.net

QNr.DomainTypeNS used
1
net
NS
e.root-servers.net (2001:500:a8::e)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
f1g1ns1.dnspod.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.dnsv2.com, ns2.dnsv2.com
3
f1g1ns2.dnspod.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.dnsv2.com, ns2.dnsv2.com
4
com
NS
k.root-servers.net (2001:7fd::1)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
5
ns1.dnsv2.com: 101.226.220.13, 129.211.176.248, 162.14.24.245, 183.192.164.118, 223.166.151.17, 223.166.151.18, 61.129.8.141
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: ns2.dnsv2.com
111.30.142.15, 183.192.164.118, 220.249.242.11, 58.247.212.37, 59.36.120.143, 61.151.180.45
6
f1g1ns1.dnspod.net: 129.211.176.187, 14.215.150.17, 14.215.155.156, 14.215.155.170, 183.192.164.117, 58.247.212.36, 61.151.180.44
A
ns1.dnsv2.com (129.211.176.248)
7
f1g1ns1.dnspod.net: No AAAA record found
AAAA
ns1.dnsv2.com (129.211.176.248)
8
f1g1ns2.dnspod.net: 101.226.220.16, 129.211.176.224, 14.215.155.203, 162.14.24.230, 183.192.201.90, 58.247.212.119, 58.247.212.48
A
ns1.dnsv2.com (129.211.176.248)
9
f1g1ns2.dnspod.net: No AAAA record found
AAAA
ns1.dnsv2.com (129.211.176.248)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
youngame.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=d6c268b4-5f26-4a83-a936-22288c2eff2c


Last Result: https://check-your-website.server-daten.de/?q=c3cdn.ml.youngame.com - 2020-07-27 20:35:39


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=c3cdn.ml.youngame.com" target="_blank">Check this Site: c3cdn.ml.youngame.com</a>