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

...

skip EDNS-Check

skip Content-Check

check links

Private IP-Address found

Checked:
13.03.2025 00:12:23

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
staging1.sqfaas.dev	A	10.140.134.13 No Hostname found	yes	1	0
	AAAA		yes
www.staging1.sqfaas.dev		Name Error	yes	1	0
*.sqfaas.dev	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.staging1.sqfaas.dev	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


	3 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 26470, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 02.04.2025, 00:00:00 +, Signature-Inception: 12.03.2025, 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: dev
dev	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.03.2025, 17:00:00 +, Signature-Inception: 12.03.2025, 16:00:00 +, KeyTag 26470, Signer-Name: (root)


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 61918, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 31.03.2025, 10:06:31 +, Signature-Inception: 09.03.2025, 10:06:31 +, KeyTag 60074, Signer-Name: dev


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


	• Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest "uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: sqfaas.dev
sqfaas.dev	1 DS RR in the parent zone found


	DS with Algorithm 8, KeyTag 11336, DigestType 2 and Digest gcqsWNpE4Z6JkU7uemuA83ionvUn4oQiZ8Ie5TQhvhg=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner sqfaas.dev., Algorithm: 8, 2 Labels, original TTL: 1800 sec, Signature-expiration: 31.03.2025, 10:06:31 +, Signature-Inception: 09.03.2025, 10:06:31 +, KeyTag 61918, Signer-Name: dev


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


	2 DNSKEY RR found


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


	Public Key with Algorithm 8, KeyTag 18888, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner sqfaas.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 11336, Signer-Name: sqfaas.dev


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


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

Zone: staging1.sqfaas.dev
staging1.sqfaas.dev	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 "ncca4b0lgrcglrfga1324r9218fldaec" between the hashed NSEC3-owner "ncca4b0lgrcglrfga1324r9218fldaec" and the hashed NextOwner "o66fl6ci77l55b847b9qt7s5agvg4i21". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	0 DNSKEY RR found





	RRSIG Type 1 validates the A - Result: 10.140.134.13 Validated: RRSIG-Owner staging1.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ncca4b0lgrcglrfga1324r9218fldaec" equal the hashed NSEC3-owner "ncca4b0lgrcglrfga1324r9218fldaec" and the hashed NextOwner "o66fl6ci77l55b847b9qt7s5agvg4i21". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NoData-Proof required and found.


	TXT-Query sends a valid NSEC3 RR as result with the hashed query name "ncca4b0lgrcglrfga1324r9218fldaec" equal the hashed NSEC3-owner "ncca4b0lgrcglrfga1324r9218fldaec" and the hashed NextOwner "o66fl6ci77l55b847b9qt7s5agvg4i21". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NoData-Proof required and found.


	AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "ncca4b0lgrcglrfga1324r9218fldaec" equal the hashed NSEC3-owner "ncca4b0lgrcglrfga1324r9218fldaec" and the hashed NextOwner "o66fl6ci77l55b847b9qt7s5agvg4i21". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NoData-Proof required and found.


	TLSA-Query (_443._tcp.staging1.sqfaas.dev) sends a valid NSEC3 RR as result with the hashed owner name "ncca4b0lgrcglrfga1324r9218fldaec" (unhashed: staging1.sqfaas.dev). So that's the Closest Encloser of the query name. Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "8lbgo2gque0vkblc6shvt5tltta88htq" (unhashed: _tcp.staging1.sqfaas.dev) with the owner "7bmnaj4414t2ao63h22clq20oatbai3j" and the NextOwner "bobkga54s6rqepjuf2il3cppgikq3jip". So that NSEC3 confirms the not-existence of the Next Closer Name. Bitmap: A, RRSIG Validated: RRSIG-Owner 7bmnaj4414t2ao63h22clq20oatbai3j.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NXDomain-Proof required and found.


	TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "5mghc8sl4pu95n8he70jbv28c8kj9a6n" (unhashed: *.staging1.sqfaas.dev) with the owner "u9p62dn4bpevgq1c9dj273atcg88unoi" and the NextOwner "7bmnaj4414t2ao63h22clq20oatbai3j". So that NSEC3 confirms the not-existence of the Wildcard expansion. Bitmap: A, RRSIG Validated: RRSIG-Owner u9p62dn4bpevgq1c9dj273atcg88unoi.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NXDomain-Proof required and found.


	CAA-Query sends a valid NSEC3 RR as result with the hashed query name "ncca4b0lgrcglrfga1324r9218fldaec" equal the hashed NSEC3-owner "ncca4b0lgrcglrfga1324r9218fldaec" and the hashed NextOwner "o66fl6ci77l55b847b9qt7s5agvg4i21". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists). Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	Status: Good. NoData-Proof required and found.

Zone: www.staging1.sqfaas.dev
www.staging1.sqfaas.dev	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 "9q5u5mpjajmraftajl2hps8e8asigpf7" between the hashed NSEC3-owner "7bmnaj4414t2ao63h22clq20oatbai3j" and the hashed NextOwner "bobkga54s6rqepjuf2il3cppgikq3jip". So the parent zone confirmes the not-existence of a DS RR. Bitmap: A, RRSIG Validated: RRSIG-Owner 7bmnaj4414t2ao63h22clq20oatbai3j.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ncca4b0lgrcglrfga1324r9218fldaec" as Owner. That's the Hash of "staging1.sqfaas.dev" with the NextHashedOwnerName "o66fl6ci77l55b847b9qt7s5agvg4i21". So that domain name is the Closest Encloser of "www.staging1.sqfaas.dev". Opt-Out: False. Bitmap: A, RRSIG Validated: RRSIG-Owner ncca4b0lgrcglrfga1324r9218fldaec.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev


	The ClosestEncloser says, that "*.staging1.sqfaas.dev" with the Hash "5mghc8sl4pu95n8he70jbv28c8kj9a6n" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "u9p62dn4bpevgq1c9dj273atcg88unoi" and the Next Owner "7bmnaj4414t2ao63h22clq20oatbai3j", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False. Bitmap: A, RRSIG Validated: RRSIG-Owner u9p62dn4bpevgq1c9dj273atcg88unoi.sqfaas.dev., Algorithm: 8, 3 Labels, original TTL: 300 sec, Signature-expiration: 02.04.2025, 06:22:34 +, Signature-Inception: 11.03.2025, 06:22:34 +, KeyTag 18888, Signer-Name: sqfaas.dev

3. Name Servers

Domain	Nameserver	NS-IP
www.staging1.sqfaas.dev	• ns-cloud-c1.googledomains.com
staging1.sqfaas.dev	• ns-cloud-c1.googledomains.com	216.239.32.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6c Mountain View/California/United States (US) - Google LLC	•
sqfaas.dev	• ns-cloud-c1.googledomains.com	216.239.32.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c2.googledomains.com	216.239.34.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c3.googledomains.com	216.239.36.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6c Mountain View/California/United States (US) - Google LLC	•
	• ns-cloud-c4.googledomains.com	216.239.38.108 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6c Mountain View/California/United States (US) - Google LLC	•
dev	• ns-tld1.charlestonroadregistry.com		•
	• ns-tld2.charlestonroadregistry.com		•
	• ns-tld3.charlestonroadregistry.com		•
	• ns-tld4.charlestonroadregistry.com		•
	• ns-tld5.charlestonroadregistry.com		•

4. SOA-Entries

Domain:	dev
Zone-Name:	dev
Primary:	ns-tld1.charlestonroadregistry.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	5

Domain:	sqfaas.dev
Zone-Name:	sqfaas.dev
Primary:	ns-cloud-c1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	8

Domain:	staging1.sqfaas.dev
Zone-Name:	sqfaas.dev
Primary:	ns-cloud-c1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	2

Domain:	www.staging1.sqfaas.dev
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

Domainname	Http-Status	redirect	Sec.	G
•

7. Comments

	1. General Results, most used to calculate the result
A	name "staging1.sqfaas.dev" is subdomain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 15 (complete: 263653)
A	Good: No asked Authoritative Name Server had a timeout
A	DNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
A	Excellent: Main Domain is in the Google-Preload-List
A	Excellent: Main Domain is in the Mozilla/Firefox-Preload-List
A	HSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Y	staging1.sqfaas.dev	10.140.134.13	Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 10.0.0.0 to 10.255.255.255: Class A - one private net with 16.777.216 adresses
B	No _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.staging1.sqfaas.dev
	2. Header-Checks
U			No https result with http status 2 or 4 (standard-check) found, no header checked.
	3. DNS- and NameServer - Checks
A	Info:: 13 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
A	Info:: 13 Queries complete, 13 with IPv6, 0 with IPv4.
A	Good: All DNS Queries done via IPv6.
	Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
A	Info:: 4 different Name Servers found: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in Delegation: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 4 Name Servers included in 1 Zone definitions: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com, 1 Name Servers listed in SOA.Primary: ns-cloud-c1.googledomains.com.
A	Good: Only one SOA.Primary Name Server found.: ns-cloud-c1.googledomains.com.
A	Good: SOA.Primary Name Server included in the delegation set.: ns-cloud-c1.googledomains.com.
A	Good: 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: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com
A	Good: All Name Server Domain Names have a Public Suffix.
A	Good: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
A	Good: All Name Server ip addresses are public.
A	Good: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 4 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.: 4 Name Servers, 1 Top Level Domain: com
	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: googledomains.com
	Warning: All Name Servers from the same Country / IP location.: 4 Name Servers, 1 Countries: US
A	Info: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 4 different subnets (first three Bytes): 216.239.32., 216.239.34., 216.239.36., 216.239.38.
A	Good: Name Server IPv4-addresses from different subnet found:
A	Info: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2001:, 1 different subnets (first two blocks): 2001:4860:, 1 different subnets (first three blocks): 2001:4860:4802:, 4 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 2 good Nameserver
A	Good: Nameserver supports Echo Capitalization: 2 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: ns-cloud-c1.googledomains.com: 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.
A	Good: 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.
	4. Content- and Performance-critical Checks
A	Good: 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
A	Duration: 99200 milliseconds, 99.200 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" > of the last months 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. Html-Parsing via https://validator.w3.org/nu/

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com

QNr.	Domain	Type	NS used
1	com	NS	b.root-servers.net (2001:500:200::b)
	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	ns-cloud-c1.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
3	ns-cloud-c2.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
4	ns-cloud-c3.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
5	ns-cloud-c4.googledomains.com	NS	a.gtld-servers.net (2001:503:a83e::2:30)
	Answer: ns5.googledomains.com, ns6.googledomains.com, ns7.googledomains.com, ns8.googledomains.com
	Answer: ns5.googledomains.com 2001:4860:4802:32::a, 216.239.32.10
	Answer: ns6.googledomains.com 2001:4860:4802:34::a, 216.239.34.10
	Answer: ns7.googledomains.com 2001:4860:4802:36::a, 216.239.36.10
	Answer: ns8.googledomains.com 2001:4860:4802:38::a, 216.239.38.10
6	ns-cloud-c1.googledomains.com: 216.239.32.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
7	ns-cloud-c1.googledomains.com: 2001:4860:4802:32::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
8	ns-cloud-c2.googledomains.com: 216.239.34.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
9	ns-cloud-c2.googledomains.com: 2001:4860:4802:34::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
10	ns-cloud-c3.googledomains.com: 216.239.36.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
11	ns-cloud-c3.googledomains.com: 2001:4860:4802:36::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
12	ns-cloud-c4.googledomains.com: 216.239.38.108	A	ns5.googledomains.com (2001:4860:4802:32::a)
13	ns-cloud-c4.googledomains.com: 2001:4860:4802:38::6c	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)

14. CAA - Entries

Domainname	Value	∑ Queries
staging1.sqfaas.dev	no CAA entry found	1
sqfaas.dev	no CAA entry found	1
dev	no CAA entry found	1

15. TXT - Entries

Domainname	Status	∑ Queries
sqfaas.dev	ok	1
staging1.sqfaas.dev	ok	1
_acme-challenge.staging1.sqfaas.dev	Name Error - The domain name does not exist	1
_acme-challenge.staging1.sqfaas.dev.sqfaas.dev	Name Error - The domain name does not exist	1
_acme-challenge.staging1.sqfaas.dev.staging1.sqfaas.dev	Name Error - The domain name does not exist	1

16. DomainService - Entries

No DomainServiceEntries entries found

17. Cipher Suites

No Ciphers found

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

Permalink: https://check-your-website.server-daten.de/?i=fa9f3476-1ac7-4d1a-bb70-617716335424

Last Result: https://check-your-website.server-daten.de/?q=staging1.sqfaas.dev - 2025-03-13 00:12:23

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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

QR-Code of this page - https://check-your-website.server-daten.de/?d=staging1.sqfaas.dev