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



T

Timeout

Checked:
17.10.2020 22:30:27


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
primeribcookie.synology.me
A
138.88.146.113
Germantown/Maryland/United States (US) - Verizon Communications
Hostname: pool-138-88-146-113.washdc.fios.verizon.net
yes
1
0

AAAA

yes


www.primeribcookie.synology.me

Name Error
yes
1
0
www.primeribcookie.synology.me
A
138.88.146.113
Germantown/Maryland/United States (US) - Verizon Communications
No Hostname found
no


*.primeribcookie.synology.me
A
138.88.146.113
yes



AAAA

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 26116, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.11.2020, 00:00:00 +, Signature-Inception: 11.10.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: me
me
3 DS RR in the parent zone found



DS with Algorithm 7, KeyTag 2569, DigestType 1 and Digest CboetNIEAmIIgf2YSJlEF4ANsmo=



DS with Algorithm 7, KeyTag 2569, DigestType 2 and Digest lOeYEG8DNQDmdWexl66RMsDpFnZNx0PFWp7KPHv1WeI=



DS with Algorithm 7, KeyTag 53233, DigestType 2 and Digest GXAJBy1Nve1lYgWLG05IaOIzXFJHkcR4/5D+FePZ7t4=



1 RRSIG RR to validate DS RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.10.2020, 17:00:00 +, Signature-Inception: 17.10.2020, 16:00:00 +, KeyTag 26116, Signer-Name: (root)



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



4 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 44634, Flags 256



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



Public Key with Algorithm 7, KeyTag 50310, Flags 256



Public Key with Algorithm 7, KeyTag 53233, Flags 257 (SEP = Secure Entry Point)



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner me., Algorithm: 8, 1 Labels, original TTL: 900 sec, Signature-expiration: 05.11.2020, 15:21:23 +, Signature-Inception: 15.10.2020, 14:21:23 +, KeyTag 45352, Signer-Name: me



RRSIG-Owner me., Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 05.11.2020, 15:21:23 +, Signature-Inception: 15.10.2020, 14:21:23 +, KeyTag 53233, Signer-Name: me



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



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 53233 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 53233, DigestType 2 and Digest "GXAJBy1Nve1lYgWLG05IaOIzXFJHkcR4/5D+FePZ7t4=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: synology.me
synology.me
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 "483mluc2de6mvkn4q8bgsfp856adurvb" between the hashed NSEC3-owner "481i380gm2at6t0oo85hckgsptoc9e3m" and the hashed NextOwner "4841du46o2aedhq9jivdm0h2nn2be0gr". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 481i380gm2at6t0oo85hckgsptoc9e3m.me., Algorithm: 8, 2 Labels, original TTL: 8400 sec, Signature-expiration: 05.11.2020, 15:21:23 +, Signature-Inception: 15.10.2020, 14:21:23 +, KeyTag 44634, Signer-Name: me



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "483mluc2de6mvkn4q8bgsfp856adurvb" between the hashed NSEC3-owner "481i380gm2at6t0oo85hckgsptoc9e3m" and the hashed NextOwner "4841du46o2aedhq9jivdm0h2nn2be0gr". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 481i380gm2at6t0oo85hckgsptoc9e3m.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 05.11.2020, 15:21:23 +, Signature-Inception: 15.10.2020, 14:21:23 +, KeyTag 50310, Signer-Name: me



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "c0aa63slu8ucpmm55hrueae8tj5iopm2" as Owner. That's the Hash of "me" with the NextHashedOwnerName "c0cj2fpum2vcgjokcgsqspku2r8bi8nt". So that domain name is the Closest Encloser of "synology.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner c0aa63slu8ucpmm55hrueae8tj5iopm2.me., Algorithm: 8, 2 Labels, original TTL: 8400 sec, Signature-expiration: 07.11.2020, 20:29:34 +, Signature-Inception: 17.10.2020, 19:29:34 +, KeyTag 44634, Signer-Name: me



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "c0aa63slu8ucpmm55hrueae8tj5iopm2" as Owner. That's the Hash of "me" with the NextHashedOwnerName "c0cj2fpum2vcgjokcgsqspku2r8bi8nt". So that domain name is the Closest Encloser of "synology.me". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner c0aa63slu8ucpmm55hrueae8tj5iopm2.me., Algorithm: 7, 2 Labels, original TTL: 8400 sec, Signature-expiration: 07.11.2020, 20:29:34 +, Signature-Inception: 17.10.2020, 19:29:34 +, KeyTag 50310, Signer-Name: me



0 DNSKEY RR found




Zone: primeribcookie.synology.me
primeribcookie.synology.me
0 DS RR in the parent zone found



0 DNSKEY RR found




Zone: www.primeribcookie.synology.me
www.primeribcookie.synology.me
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.primeribcookie.synology.me
  ddns-ns1.quickconnect.to

primeribcookie.synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC

synology.me
  ddns-ns1.quickconnect.to
157.245.20.209
Frankfurt am Main/Hesse/Germany (DE) - DigitalOcean, LLC


  ddns-ns2.quickconnect.to
68.183.254.129
London/England/United Kingdom (GB) - DigitalOcean, LLC

me
  a0.nic.me / ns009b.app23.nrt1.afilias-nst.info


  a2.nic.me / LHR6


  b0.nic.me / ns009b.app9.ams2.afilias-nst.info


  b2.nic.me / LHR6


  c0.nic.me / ns009b.app8.ams2.afilias-nst.info


  ns.nic.me


4. SOA-Entries


Domain:me
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:me
Zone-Name:me
Primary:ns.nic.me
Mail:noc.afilias-nst.info
Serial:2010994209
Refresh:3600
Retry:3600
Expire:3600000
TTL:8400
num Entries:5


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:525172592
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:525172594
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:primeribcookie.synology.me
Zone-Name:synology.me
Primary:ddns-ns1.quickconnect.to
Mail:domain.synology.com
Serial:525172673
Refresh:3600
Retry:300
Expire:6040000
TTL:3600
num Entries:1


Domain:www.primeribcookie.synology.me
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
• http://primeribcookie.synology.me/
138.88.146.113
-14

10.014
T
Timeout - The operation has timed out

• http://www.primeribcookie.synology.me/
138.88.146.113
-14

10.014
T
Timeout - The operation has timed out

• https://primeribcookie.synology.me/
138.88.146.113
-14

10.014
T
Timeout - The operation has timed out

• https://www.primeribcookie.synology.me/
138.88.146.113
-14

10.017
T
Timeout - The operation has timed out

• http://primeribcookie.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
138.88.146.113
-14

10.060
T
Timeout - The operation has timed out
Visible Content:

• http://www.primeribcookie.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
138.88.146.113
-14

10.030
T
Timeout - The operation has timed out
Visible Content:

• https://138.88.146.113/
138.88.146.113
-14

10.000
T
Timeout - The operation has timed out

7. Comments


1. General Results, most used to calculate the result

Aname "primeribcookie.synology.me" is domain, public suffix is ".synology.me", top-level-domain is ".me", top-level-domain-type is "country-code", Country is Montenegro, tld-manager is "Government of Montenegro", num .me-domains preloaded: 1530 (complete: 131120)
Agood: All ip addresses are public addresses
Warning: Only one ip address found: primeribcookie.synology.me has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: primeribcookie.synology.me has no ipv6 address.
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.
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain primeribcookie.synology.me, 1 ip addresses.

2. DNS- and NameServer - Checks

AInfo:: 23 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 23 Queries complete, 21 with IPv6, 2 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.
Bad (greater 8):: An average of 11.5 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 2 Name Servers included in Delegation: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 2 Name Servers included in 1 Zone definitions: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to, 1 Name Servers listed in SOA.Primary: ddns-ns1.quickconnect.to.
AGood: Only one SOA.Primary Name Server found.: ddns-ns1.quickconnect.to.
AGood: SOA.Primary Name Server included in the delegation set.: ddns-ns1.quickconnect.to.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to
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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 2 Name Servers, 1 Top Level Domain: to
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: quickconnect.to
AGood: Name servers with different Country locations found: 2 Name Servers, 2 Countries: DE, GB
AInfo: Ipv4-Subnet-list: 2 Name Servers, 2 different subnets (first Byte): 157., 68., 2 different subnets (first two Bytes): 157.245., 68.183., 2 different subnets (first three Bytes): 157.245.20., 68.183.254.
AExcellent: Every Name Server IPv4-address starts with an unique Byte.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ddns-ns1.quickconnect.to: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns.nic.me: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Agood: CAA entries found, creating certificate is limited: letsencrypt.org is allowed to create certificates

3. Content- and Performance-critical Checks

http://primeribcookie.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 138.88.146.113
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.primeribcookie.synology.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 138.88.146.113
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 128793 milliseconds, 128.793 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)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
1
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2001370351
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-10-17 19:06:28
2021-01-15 19:06:28
primeribcookie.synology.me - 1 entries



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

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
3522302269
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-10-17 17:06:28
2021-01-15 18:06:28
primeribcookie.synology.me
1 entries



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: ddns-ns1.quickconnect.to, ddns-ns2.quickconnect.to

QNr.DomainTypeNS used
1
to
NS
h.root-servers.net (2001:500:1::53)

Answer: colo.tonic.to, frankfurt.tonic.to, helsinki.tonic.to, newyork.tonic.to, singapore.tonic.to, sydney.tonic.to, tonic.to
2
ddns-ns1.quickconnect.to
NS
colo.tonic.to (216.74.32.101)

Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
3
ddns-ns2.quickconnect.to
NS
colo.tonic.to (216.74.32.101)

Answer: ns-1412.awsdns-48.org, ns-1987.awsdns-56.co.uk, ns-55.awsdns-06.com, ns-597.awsdns-10.net
4
org
NS
f.root-servers.net (2001:500:2f::f)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
5
ns-1412.awsdns-48.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1075.awsdns-48.org, g-ns-1648.awsdns-48.org, g-ns-176.awsdns-48.org, g-ns-754.awsdns-48.org

Answer: g-ns-1075.awsdns-48.org
205.251.196.51, 2600:9000:5304:3300::1

Answer: g-ns-1648.awsdns-48.org
205.251.198.112, 2600:9000:5306:7000::1

Answer: g-ns-176.awsdns-48.org
205.251.192.176, 2600:9000:5300:b000::1

Answer: g-ns-754.awsdns-48.org
205.251.194.242, 2600:9000:5302:f200::1
6
uk
NS
m.root-servers.net (2001:dc3::35)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
7
ns-1987.awsdns-56.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1531.awsdns-56.co.uk, g-ns-1852.awsdns-56.co.uk, g-ns-376.awsdns-56.co.uk, g-ns-952.awsdns-56.co.uk

Answer: g-ns-1531.awsdns-56.co.uk
205.251.197.251, 2600:9000:5305:fb00::1

Answer: g-ns-1852.awsdns-56.co.uk
205.251.199.60, 2600:9000:5307:3c00::1

Answer: g-ns-376.awsdns-56.co.uk
205.251.193.120, 2600:9000:5301:7800::1

Answer: g-ns-952.awsdns-56.co.uk
205.251.195.184, 2600:9000:5303:b800::1
8
com
NS
c.root-servers.net (2001:500:2::c)

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
9
ns-55.awsdns-06.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1158.awsdns-06.com, g-ns-1734.awsdns-06.com, g-ns-582.awsdns-06.com, g-ns-7.awsdns-06.com

Answer: g-ns-1158.awsdns-06.com
205.251.196.134, 2600:9000:5304:8600::1

Answer: g-ns-1734.awsdns-06.com
205.251.198.198, 2600:9000:5306:c600::1

Answer: g-ns-582.awsdns-06.com
205.251.194.70, 2600:9000:5302:4600::1

Answer: g-ns-7.awsdns-06.com
205.251.192.7, 2600:9000:5300:700::1
10
net
NS
l.root-servers.net (2001:500:9f::42)

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
11
ns-597.awsdns-10.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1354.awsdns-10.net, g-ns-1930.awsdns-10.net, g-ns-459.awsdns-10.net, g-ns-780.awsdns-10.net

Answer: g-ns-1354.awsdns-10.net
205.251.197.74, 2600:9000:5305:4a00::1

Answer: g-ns-1930.awsdns-10.net
205.251.199.138, 2600:9000:5307:8a00::1

Answer: g-ns-459.awsdns-10.net
205.251.193.203, 2600:9000:5301:cb00::1

Answer: g-ns-780.awsdns-10.net
205.251.195.12, 2600:9000:5303:c00::1
12
ns-1412.awsdns-48.org: 205.251.197.132
A
g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
13
ns-1412.awsdns-48.org: 2600:9000:5305:8400::1
AAAA
g-ns-1075.awsdns-48.org (2600:9000:5304:3300::1)
14
ns-1987.awsdns-56.co.uk: 205.251.199.195
A
g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
15
ns-1987.awsdns-56.co.uk: 2600:9000:5307:c300::1
AAAA
g-ns-1531.awsdns-56.co.uk (2600:9000:5305:fb00::1)
16
ns-55.awsdns-06.com: 205.251.192.55
A
g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
17
ns-55.awsdns-06.com: 2600:9000:5300:3700::1
AAAA
g-ns-1158.awsdns-06.com (2600:9000:5304:8600::1)
18
ns-597.awsdns-10.net: 205.251.194.85
A
g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
19
ns-597.awsdns-10.net: 2600:9000:5302:5500::1
AAAA
g-ns-1354.awsdns-10.net (2600:9000:5305:4a00::1)
20
ddns-ns1.quickconnect.to: 157.245.20.209
A
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
21
ddns-ns1.quickconnect.to: No AAAA record found
AAAA
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
22
ddns-ns2.quickconnect.to: 68.183.254.129
A
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)
23
ddns-ns2.quickconnect.to: No AAAA record found
AAAA
ns-1412.awsdns-48.org (2600:9000:5305:8400::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
primeribcookie.synology.me
0

no CAA entry found
1
0
synology.me
5
issue
letsencrypt.org
1
0
me
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
primeribcookie.synology.me

ok
1
0
_acme-challenge.primeribcookie.synology.me

missing entry or wrong length
1
0
_acme-challenge.primeribcookie.synology.me.primeribcookie.synology.me

perhaps wrong
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=9d42f339-edd1-486d-b47f-04b2e18ed389


Last Result: https://check-your-website.server-daten.de/?q=primeribcookie.synology.me - 2020-10-17 22:30:27


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

<a href="https://check-your-website.server-daten.de/?q=primeribcookie.synology.me" target="_blank">Check this Site: primeribcookie.synology.me</a>