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

...

skip EDNS-Check

skip Content-Check

check links

Private IP-Address found

Checked:
05.08.2022 18:45:00

Older results

No older results found

1. IP-Addresses

Host	Type	IP-Address	is auth.	∑ Queries	∑ Timeout
sciencebox-jupyterhub-server-prod-us.spotify.net	A	10.205.25.106 No Hostname found	yes	1	0
	AAAA		yes
www.sciencebox-jupyterhub-server-prod-us.spotify.net		Name Error	yes	1	0
*.spotify.net	A	Name Error	yes
	AAAA	Name Error	yes
	CNAME	Name Error	yes
*.sciencebox-jupyterhub-server-prod-us.spotify.net	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 20826, Flags 256


	1 RRSIG RR to validate DNSKEY RR found


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


	DS with Algorithm 8, KeyTag 35886, DigestType 2 and Digest eGKyf19Rbr4ZaARE1M5edimBkxhCxGXwAjZAHYvZc+4=


	1 RRSIG RR to validate DS RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 05:00:00 +, Signature-Inception: 05.08.2022, 04:00:00 +, KeyTag 20826, Signer-Name: (root)


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


	2 DNSKEY RR found


	Public Key with Algorithm 8, KeyTag 4403, Flags 256


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


	1 RRSIG RR to validate DNSKEY RR found


	RRSIG-Owner net., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 17.08.2022, 16:28:30 +, Signature-Inception: 02.08.2022, 16:23:30 +, KeyTag 35886, Signer-Name: net


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


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

Zone: spotify.net
spotify.net	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 "hjekqoqajk1d2mjob716j9u3dshjvaeu" between the hashed NSEC3-owner "hjedu1l6s858m1me56ofdms42cmvfrhp" and the hashed NextOwner "hjel7anq0vu72em0a8tsi2u8ibdd38mk". So the parent zone confirmes the not-existence of a DS RR. Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner hjedu1l6s858m1me56ofdms42cmvfrhp.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 09.08.2022, 06:08:41 +, Signature-Inception: 02.08.2022, 04:58:41 +, KeyTag 4403, Signer-Name: net


	DS-Query in the parent zone sends valid NSEC3 RR with the Hash "a1rt98bs5qgc9nfi51s9hci47uljg6jh" as Owner. That's the Hash of "net" with the NextHashedOwnerName "a1rtlnpgulogn7b9a62shje1u3ttp8dr". So that domain name is the Closest Encloser of "spotify.net". Opt-Out: True. Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner a1rt98bs5qgc9nfi51s9hci47uljg6jh.net., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 11.08.2022, 06:10:13 +, Signature-Inception: 04.08.2022, 05:00:13 +, KeyTag 4403, Signer-Name: net


	0 DNSKEY RR found




Zone: sciencebox-jupyterhub-server-prod-us.spotify.net
sciencebox-jupyterhub-server-prod-us.spotify.net	0 DS RR in the parent zone found


	0 DNSKEY RR found




Zone: www.sciencebox-jupyterhub-server-prod-us.spotify.net
www.sciencebox-jupyterhub-server-prod-us.spotify.net	0 DS RR in the parent zone found

3. Name Servers

Domain	Nameserver	NS-IP
www.sciencebox-jupyterhub-server-prod-us.spotify.net	• dns1.p07.nsone.net
sciencebox-jupyterhub-server-prod-us.spotify.net	• dns1.p07.nsone.net / ns1dns-ams03-402-5303-0	198.51.44.7 New York/United States (US) - NSONE Inc	•
	•	2620:4d:4000:6259:7:7:0:1 New York/United States (US) - NSONE Inc	•
	• ns-cloud-e1.googledomains.com	216.239.32.110 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6e Beauharnois/Quebec/Canada (CA) - Google LLC	•
spotify.net	• dns1.p07.nsone.net / ns1dns-ams03-410-5303-0	198.51.44.7 New York/United States (US) - NSONE Inc	•
	•	2620:4d:4000:6259:7:7:0:1 New York/United States (US) - NSONE Inc	•
	• dns2.p07.nsone.net / ns1dns-fra03-911-5304-0	198.51.45.7 Chicago/Illinois/United States (US) - NSONE Inc	•
	•	2a00:edc0:6259:7:7::2 Amsterdam/North Holland/Netherlands (NL) - NS1	•
	• dns3.p07.nsone.net / ns1dns-ams03-410-5312-0	198.51.44.71 New York/United States (US) - NSONE Inc	•
	•	2620:4d:4000:6259:7:7:0:3 New York/United States (US) - NSONE Inc	•
	• dns4.p07.nsone.net / ns1dns-ams03-403-5311-0	198.51.45.71 Chicago/Illinois/United States (US) - NSONE Inc	•
	•	2a00:edc0:6259:7:7::4 Amsterdam/North Holland/Netherlands (NL) - NS1	•
	• ns-cloud-e1.googledomains.com	216.239.32.110 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:32::6e Beauharnois/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-e2.googledomains.com	216.239.34.110 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:34::6e Beauharnois/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-e3.googledomains.com	216.239.36.110 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:36::6e Beauharnois/Quebec/Canada (CA) - Google LLC	•
	• ns-cloud-e4.googledomains.com	216.239.38.110 Mountain View/California/United States (US) - Google LLC	•
	•	2001:4860:4802:38::6e Beauharnois/Quebec/Canada (CA) - Google LLC	•
net	• a.gtld-servers.net / nnn1-stk4		•
	• b.gtld-servers.net / nnn1-eltxl2		•
	• c.gtld-servers.net / nnn1-stk4		•
	• d.gtld-servers.net / nnn1-stk4		•
	• e.gtld-servers.net / nnn1-stk4		•
	• f.gtld-servers.net / nnn1-fra5		•
	• g.gtld-servers.net / nnn1-fra5		•
	• h.gtld-servers.net / nnn1-fra5		•
	• i.gtld-servers.net / nnn1-fra5		•
	• j.gtld-servers.net / nnn1-lon5		•
	• k.gtld-servers.net / nnn1-lon5		•
	• l.gtld-servers.net / nnn1-lon5		•
	• m.gtld-servers.net / nnn1-lon5		•

4. SOA-Entries

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

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

Domain:	spotify.net
Zone-Name:	spotify.net
Primary:	dns1.p07.nsone.net
Mail:	hostmaster.nsone.net
Serial:	1655909745
Refresh:	43200
Retry:	7200
Expire:	1209600
TTL:	3600
num Entries:	8

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

Domain:	sciencebox-jupyterhub-server-prod-us.spotify.net
Zone-Name:	spotify.net
Primary:	dns1.p07.nsone.net
Mail:	hostmaster.nsone.net
Serial:	1655909745
Refresh:	43200
Retry:	7200
Expire:	1209600
TTL:	3600
num Entries:	2

Domain:	sciencebox-jupyterhub-server-prod-us.spotify.net
Zone-Name:	spotify.net
Primary:	ns-cloud-e1.googledomains.com
Mail:	cloud-dns-hostmaster.google.com
Serial:	1
Refresh:	21600
Retry:	3600
Expire:	259200
TTL:	300
num Entries:	2

Domain:	www.sciencebox-jupyterhub-server-prod-us.spotify.net
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 "sciencebox-jupyterhub-server-prod-us.spotify.net" is subdomain, public suffix is ".net", top-level-domain is ".net", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .net-domains preloaded: 7088 (complete: 175327)
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
	HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Y	sciencebox-jupyterhub-server-prod-us.spotify.net	10.205.25.106	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
	2. DNS- and NameServer - Checks
A	Info:: 26 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 8 Name Servers.
A	Info:: 26 Queries complete, 26 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:: 8 different Name Servers found: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 8 Name Servers included in Delegation: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 8 Name Servers included in 1 Zone definitions: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com, 2 Name Servers listed in SOA.Primary: dns1.p07.nsone.net, ns-cloud-e1.googledomains.com.
	Error: Different SOA.Primary Name Servers found, different SOA Definitions.: dns1.p07.nsone.net,ns-cloud-e1.googledomains.com.
	Error: SOA.Primary Name Server not included in the delegation set.: dns1.p07.nsone.net,ns-cloud-e1.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: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.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: 8 different Name Servers found
A	Good: All name servers have ipv4- and ipv6-addresses.: 8 different Name Servers found
A	Good: Name servers with different Top Level Domains / Public Suffix List entries found: 8 Name Servers, 2 Top Level Domains: net, com
A	Good: Name Servers with different domain names found.: 2 different Domains found
A	Good: Name servers with different Country locations found: 8 Name Servers, 3 Countries: CA, NL, US
A	Info: Ipv4-Subnet-list: 8 Name Servers, 2 different subnets (first Byte): 198., 216., 2 different subnets (first two Bytes): 198.51., 216.239., 6 different subnets (first three Bytes): 198.51.44., 198.51.45., 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: 8 Name Servers with IPv6, 3 different subnets (first block): 2001:, 2620:, 2a00:, 3 different subnets (first two blocks): 2001:4860:, 2620:004d:, 2a00:edc0:, 3 different subnets (first three blocks): 2001:4860:4802:, 2620:004d:4000:, 2a00:edc0:6259:, 6 different subnets (first four blocks): 2001:4860:4802:0032:, 2001:4860:4802:0034:, 2001:4860:4802:0036:, 2001:4860:4802:0038:, 2620:004d:4000:6259:, 2a00:edc0:6259:0007:
A	Good: Name Server IPv6 addresses from different subnets found.
A	Good: Nameserver supports TCP connections: 4 good Nameserver
A	Info: Nameserver mit different domain names found. May be a problem with DNS-Updates
A	Good: Nameserver supports Echo Capitalization: 4 good Nameserver
A	Good: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
A	Good: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
	Nameserver doesn't pass all EDNS-Checks: dns1.p07.nsone.net: 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.
X	Fatal error: Nameservers with different SOA Serial Numbers
	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
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: 102277 milliseconds, 102.277 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

Issuer				last 7 days	active	num Certs
CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US				0	3	5
CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US				0	0	2

CRT-Id	Issuer	not before	not after	Domain names	LE-Duplicate	next LE
6856162059 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-05-16 22:00:00	2023-05-17 21:59:59	*.spotify.net, spotify.net 2 entries
6460517173 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-03-28 22:00:00	2023-03-29 21:59:59	*.spotify.net, spotify.net 2 entries
6062484124 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2022-01-19 23:00:00	2023-01-20 22:59:59	*.spotify.net, spotify.net 2 entries
4911909616 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2021-06-07 22:00:00	2022-07-09 21:59:59	*.spotify.net, spotify.net 2 entries
4456219187 leaf cert	CN=DigiCert TLS RSA SHA256 2020 CA1, O=DigiCert Inc, C=US	2021-04-27 22:00:00	2022-04-28 21:59:59	*.spotify.net, spotify.net 2 entries
3037414606 leaf cert	CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US	2020-06-22 22:00:00	2021-09-02 10:00:00	*.spotify.net, spotify.net 2 entries
140922926 leaf cert	CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US	2017-05-15 22:00:00	2020-07-29 10:00:00	*.spotify.net, spotify.net 2 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: dns1.p07.nsone.net, dns2.p07.nsone.net, dns3.p07.nsone.net, dns4.p07.nsone.net, ns-cloud-e1.googledomains.com, ns-cloud-e2.googledomains.com, ns-cloud-e3.googledomains.com, ns-cloud-e4.googledomains.com

QNr.	Domain	Type	NS used
1	net	NS	g.root-servers.net (2001:500:12::d0d)
	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	dns1.p07.nsone.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
	Answer: dns1.p01.nsone.net 198.51.44.1, 2620:4d:4000:6259:7:1:0:1
	Answer: dns2.p01.nsone.net 198.51.45.1, 2a00:edc0:6259:7:1::2
	Answer: dns3.p01.nsone.net 198.51.44.65, 2620:4d:4000:6259:7:1:0:3
	Answer: dns4.p01.nsone.net 198.51.45.65, 2a00:edc0:6259:7:1::4
3	dns2.p07.nsone.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
	Answer: dns1.p01.nsone.net 198.51.44.1, 2620:4d:4000:6259:7:1:0:1
	Answer: dns2.p01.nsone.net 198.51.45.1, 2a00:edc0:6259:7:1::2
	Answer: dns3.p01.nsone.net 198.51.44.65, 2620:4d:4000:6259:7:1:0:3
	Answer: dns4.p01.nsone.net 198.51.45.65, 2a00:edc0:6259:7:1::4
4	dns3.p07.nsone.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
	Answer: dns1.p01.nsone.net 198.51.44.1, 2620:4d:4000:6259:7:1:0:1
	Answer: dns2.p01.nsone.net 198.51.45.1, 2a00:edc0:6259:7:1::2
	Answer: dns3.p01.nsone.net 198.51.44.65, 2620:4d:4000:6259:7:1:0:3
	Answer: dns4.p01.nsone.net 198.51.45.65, 2a00:edc0:6259:7:1::4
5	dns4.p07.nsone.net	NS	l.gtld-servers.net (2001:500:d937::30)
	Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
	Answer: dns1.p01.nsone.net 198.51.44.1, 2620:4d:4000:6259:7:1:0:1
	Answer: dns2.p01.nsone.net 198.51.45.1, 2a00:edc0:6259:7:1::2
	Answer: dns3.p01.nsone.net 198.51.44.65, 2620:4d:4000:6259:7:1:0:3
	Answer: dns4.p01.nsone.net 198.51.45.65, 2a00:edc0:6259:7:1::4
6	com	NS	i.root-servers.net (2001:7fe::53)
	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
7	ns-cloud-e1.googledomains.com	NS	e.gtld-servers.net (2001:502:1ca1::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
8	ns-cloud-e2.googledomains.com	NS	e.gtld-servers.net (2001:502:1ca1::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
9	ns-cloud-e3.googledomains.com	NS	e.gtld-servers.net (2001:502:1ca1::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
10	ns-cloud-e4.googledomains.com	NS	e.gtld-servers.net (2001:502:1ca1::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
11	dns1.p07.nsone.net: 198.51.44.7	A	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
12	dns1.p07.nsone.net: 2620:4d:4000:6259:7:7:0:1	AAAA	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
13	dns2.p07.nsone.net: 198.51.45.7	A	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
14	dns2.p07.nsone.net: 2a00:edc0:6259:7:7::2	AAAA	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
15	dns3.p07.nsone.net: 198.51.44.71	A	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
16	dns3.p07.nsone.net: 2620:4d:4000:6259:7:7:0:3	AAAA	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
17	dns4.p07.nsone.net: 198.51.45.71	A	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
18	dns4.p07.nsone.net: 2a00:edc0:6259:7:7::4	AAAA	dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
19	ns-cloud-e1.googledomains.com: 216.239.32.110	A	ns5.googledomains.com (2001:4860:4802:32::a)
20	ns-cloud-e1.googledomains.com: 2001:4860:4802:32::6e	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
21	ns-cloud-e2.googledomains.com: 216.239.34.110	A	ns5.googledomains.com (2001:4860:4802:32::a)
22	ns-cloud-e2.googledomains.com: 2001:4860:4802:34::6e	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
23	ns-cloud-e3.googledomains.com: 216.239.36.110	A	ns5.googledomains.com (2001:4860:4802:32::a)
24	ns-cloud-e3.googledomains.com: 2001:4860:4802:36::6e	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)
25	ns-cloud-e4.googledomains.com: 216.239.38.110	A	ns5.googledomains.com (2001:4860:4802:32::a)
26	ns-cloud-e4.googledomains.com: 2001:4860:4802:38::6e	AAAA	ns5.googledomains.com (2001:4860:4802:32::a)

13. CAA - Entries

Domainname	Value	∑ Queries
sciencebox-jupyterhub-server-prod-us.spotify.net	no CAA entry found	1
spotify.net	no CAA entry found	1
net	no CAA entry found	1

14. TXT - Entries

Domainname	TXT Entry	Status	∑ Queries
spotify.net	google-site-verification=-iZV4qwMcOFQsF6J4_Ofem5TtOoYX8RxNYiYg73E81c	ok	1
spotify.net	MS=ms76021910	ok	1
spotify.net	v=spf1 ~all	ok	1
sciencebox-jupyterhub-server-prod-us.spotify.net		ok	1
_acme-challenge.sciencebox-jupyterhub-server-prod-us.spotify.net		Name Error - The domain name does not exist	1
_acme-challenge.sciencebox-jupyterhub-server-prod-us.spotify.net.spotify.net		Name Error - The domain name does not exist	1
_acme-challenge.sciencebox-jupyterhub-server-prod-us.spotify.net.sciencebox-jupyterhub-server-prod-us.spotify.net		Name Error - The domain name does not exist	1

15. DomainService - Entries (alpha - see server-daten.de)

No DomainServiceEntries entries found

16. Cipher Suites

No Ciphers found

17. Portchecks (OpenRelayCheck is alpha) (Some changes - now checks domain + ip address, results older 2022-07-31 15:00 may be wrong / invisible)

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

Permalink: https://check-your-website.server-daten.de/?i=10cf9c7d-4ad9-49c5-a8bb-ca79d3bf7881

Last Result: https://check-your-website.server-daten.de/?q=sciencebox-jupyterhub-server-prod-us.spotify.net - 2022-08-05 18:45:00

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

<a href="https://check-your-website.server-daten.de/?q=sciencebox-jupyterhub-server-prod-us.spotify.net" target="_blank">Check this Site: sciencebox-jupyterhub-server-prod-us.spotify.net</a>