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



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
01.07.2019 16:22:56


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
burp.triaxiomsecurity.com
A
104.236.229.66
Clifton/New Jersey/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes


www.burp.triaxiomsecurity.com
A
104.236.229.66
Clifton/New Jersey/United States (US) - DigitalOcean, LLC
No Hostname found
yes
1
0

AAAA

yes



2. DNSSEC

Zone (*)DNSSEC - Informations

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



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



Public Key with Algorithm 8, KeyTag 59944, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.07.2019, 00:00:00 +, Signature-Inception: 01.07.2019, 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



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.07.2019, 05:00:00 +, Signature-Inception: 01.07.2019, 04:00:00 +, KeyTag 59944, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 3800, 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: 06.07.2019, 18:25:33 +, Signature-Inception: 21.06.2019, 18:20:33 +, 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: triaxiomsecurity.com
triaxiomsecurity.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 "s5ns3tbmhtqe4cfjaivaab34t29ctfj5" between the hashed NSEC3-owner "s5nqi2jqlfktkh4k9fov1866plncu4at" and the hashed NextOwner "s5nttjlt8glhopt0shqh6n69t95uktmn". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner s5nqi2jqlfktkh4k9fov1866plncu4at.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 06.07.2019, 05:00:43 +, Signature-Inception: 29.06.2019, 03:50:43 +, KeyTag 3800, Signer-Name: com



0 DNSKEY RR found




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



0 DNSKEY RR found




Zone: www.burp.triaxiomsecurity.com
www.burp.triaxiomsecurity.com
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.burp.triaxiomsecurity.com
U  ns1.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com


U  ns2.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com

burp.triaxiomsecurity.com
U  ns1.burp.triaxiomsecurity.com
104.236.229.66
Clifton/New Jersey/United States (US) - DigitalOcean, LLC


U  ns2.burp.triaxiomsecurity.com
104.236.229.66
Clifton/New Jersey/United States (US) - DigitalOcean, LLC

triaxiomsecurity.com
  ns-cloud-b1.googledomains.com


  ns-cloud-b2.googledomains.com


  ns-cloud-b3.googledomains.com


  ns-cloud-b4.googledomains.com

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:
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1561990949
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:3


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


Domain:triaxiomsecurity.com
Zone-Name:
Primary:ns-cloud-b1.googledomains.com
Mail:cloud-dns-hostmaster.google.com
Serial:50
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:4


Domain:burp.triaxiomsecurity.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


Domain:www.burp.triaxiomsecurity.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:2


5. Screenshots

Startaddress: https://burp.triaxiomsecurity.com, address used: https://burp.triaxiomsecurity.com/, Screenshot created 2020-03-26 01:22:27 +00:0

Mobil (412px x 732px)

806 milliseconds

Screenshot mobile - https://burp.triaxiomsecurity.com/
Mobil + Landscape (732px x 412px)

834 milliseconds

Screenshot mobile landscape - https://burp.triaxiomsecurity.com/
Screen (1280px x 1680px)

937 milliseconds

Screenshot Desktop - https://burp.triaxiomsecurity.com/

Mobile- and other Chrome-Checks

widthheight
visual Viewport412732
content Size412732

Good: No horizontal scrollbar. Content-size width = visual Viewport width.

Chrome-Connection: secure. secure connection settings. The connection to this site is encrypted and authenticated using TLS 1.3, P-256, and AES_128_GCM.

Chrome-Resources : secure. all served securely. All resources on this page are served securely.

6. Url-Checks


:

:
DomainnameHttp-StatusredirectSec.G
• http://burp.triaxiomsecurity.com/
104.236.229.66
200

0.210
H
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

• http://www.burp.triaxiomsecurity.com/
104.236.229.66
200

0.210
H
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

• https://burp.triaxiomsecurity.com/
104.236.229.66
200

2.170
B
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

• https://www.burp.triaxiomsecurity.com/
104.236.229.66
200

1.543
B
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

• http://burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.236.229.66
200

0.207

Visible Content:
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

• http://www.burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
104.236.229.66
200

0.207

Visible Content:
Server: Burp Collaborator https://burpcollaborator.net/
X-Collaborator-Version: 4
Content-Type: text/html
Content-Length: 1190

7. Comments


1. General Results, most used to calculate the result

Aname "burp.triaxiomsecurity.com" is subdomain, public suffix is "com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services"
Agood: All ip addresses are public addresses
AGood: Some urls with http status 200/404 have a complete Content-Type header (MediaType / MediaSubType + correct charset):0 complete Content-Type - header (6 urls)
http://burp.triaxiomsecurity.com/ 104.236.229.66


Url with incomplete Content-Type - header - missing charset
http://www.burp.triaxiomsecurity.com/ 104.236.229.66


Url with incomplete Content-Type - header - missing charset
https://burp.triaxiomsecurity.com/ 104.236.229.66


Url with incomplete Content-Type - header - missing charset
https://www.burp.triaxiomsecurity.com/ 104.236.229.66


Url with incomplete Content-Type - header - missing charset
http://burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.236.229.66


Url with incomplete Content-Type - header - missing charset
http://www.burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.236.229.66


Url with incomplete Content-Type - header - missing charset
Bhttps://burp.triaxiomsecurity.com/ 104.236.229.66
200

Missing HSTS-Header
Bhttps://www.burp.triaxiomsecurity.com/ 104.236.229.66
200

Missing HSTS-Header
CError - no preferred version www or non-www. Select one version as preferred version, then add a redirect https + not-preferred version to https + preferred version. Perhaps in your port 443 vHost something like "RewriteEngine on" + "RewriteCond %{SERVER_NAME} = example.com" + "ReWriteRule ^ https://www.example.com%{REQUEST_URI} [END,QSA,R=permanent]" (three rows, without the "). That should create a redirect https + example.com ⇒ https + www.example.com. Or switch both values to use the non-www version as your preferred version.
CError - more then one version with Http-Status 200. After all redirects, all users (and search engines) should see the same https url: Non-www or www, but not both with http status 200.
HFatal error: http result with http-status 200, no encryption. Add a redirect http ⇒ https, so every connection is secure. Perhaps in your port 80 vHost something like "RewriteEngine on" + "RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,QSA,R=permanent]" (two rows, without the "). Don't add this in your port 443 vHost, that would create a loop.
OOld connection: SHA1 as Hash Algorithm is deprecated. Switch to SHA256 or SHA384. If your certificate has SHA256, first check your domain via ssllabs.com and update weak Cipher Suites. Forward Secrecy support is required. The part "Cipher Suites" should have a preference. First Cipher Suite with SHA instead of SHA256 or higher - that's the problem, change that. If that doesn't help, check if there is an old Firewall / router or something else, that supports only SHA1. Update that component.
XFatal error: Nameserver doesn't support TCP connection: ns1.burp.triaxiomsecurity.com / 104.236.229.66: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 104.236.229.66:53
XFatal error: Nameserver doesn't support TCP connection: ns1.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 104.236.229.66:53
XFatal error: Nameserver doesn't support TCP connection: ns2.burp.triaxiomsecurity.com / 104.236.229.66: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 104.236.229.66:53
XFatal error: Nameserver doesn't support TCP connection: ns2.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com: Fatal error - no NameServer IP-Address or connection. Details: One or more errors occurred. - No connection could be made because the target machine actively refused it 104.236.229.66:53

2. DNS- and NameServer - Checks

AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.burp.triaxiomsecurity.com / 104.236.229.66: 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: ns1.burp.triaxiomsecurity.com.burp.triaxiomsecurity.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.
Nameserver doesn't pass all EDNS-Checks: ns2.burp.triaxiomsecurity.com / 104.236.229.66: 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: ns2.burp.triaxiomsecurity.com.burp.triaxiomsecurity.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.
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

http://burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.236.229.66
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.burp.triaxiomsecurity.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 104.236.229.66
200

Warning: Not existing ACME-file, but Server sends 200, not 404 or redirect. May be a problem creating a Letsencrypt certificate. Checking /.well-known/acme-challenge/random-filename - a http status 404 - Not Found - is expected. If your server sends content and a http status 200, the validation file (87 bytes, token, dot and the hash of the public part of the account key) may be invisible, so Letsencrypt can't validate your domain. If it is an application that sends this content, perhaps create an exception, so /.well-known/acme-challenge sends raw files. Or create a redirect to another domain and / or port 443, but your Letsencrypt client must support such a solution. Certbot: Use webroot as authenticator - https://certbot.eff.org/docs/using.html 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: 133556 milliseconds, 133.556 seconds


8. Connections

DomainIPPortCert.ProtocolKeyExchangeStrengthCipherStrengthHashAlgorithmOCSP stapling
Domain/KeyExchangeIP/StrengthPort/CipherCert./StrengthProtocol/HashAlgorithmOCSP stapling
burp.triaxiomsecurity.com
104.236.229.66
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
burp.triaxiomsecurity.com
104.236.229.66
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - duplicate certificates
1CN=burp.triaxiomsecurity.com

2CN=burp.triaxiomsecurity.com

3CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


www.burp.triaxiomsecurity.com
104.236.229.66
443
ok
Tls12
ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak

www.burp.triaxiomsecurity.com
104.236.229.66
443
ok
Tls12

ECDH Ephermal
384
Aes256
256
Sha1
error checking OCSP stapling
weak
 
no Tls.1.2
no Tls.1.1
no Tls.1.0

no Tls.1.2
no Tls.1.1
no Tls.1.0
Chain - duplicate certificates
1CN=burp.triaxiomsecurity.com

2CN=burp.triaxiomsecurity.com

3CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US


9. Certificates

1.
1.
CN=burp.triaxiomsecurity.com
11.04.2019
10.07.2019
398 days expired
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com - 2 entries
1.
1.
CN=burp.triaxiomsecurity.com
11.04.2019

10.07.2019
398 days expired
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com - 2 entries

KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:042976B3E5AA1AAA5A246339150FA5102E60
Thumbprint:AF5A1CC7B1CAB26C751E84241F58B425D6178539
SHA256 / Certificate:WZaoGzlR1NYbdq5l6vNi27JtMv057zAL7mCDZU4DOAE=
SHA256 hex / Cert (DANE * 0 1):e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
SHA256 hex / PublicKey (DANE * 1 1):83a2e88d4f9c4b05280527544b961efe4207d4d936e7cc47df1cf685bd4002aa
SHA256 hex / Subject Public Key Information (SPKI):1eb22ea42d9dc5b358afcf7dcc3d817f4f4737bde4f560842b868f9ffcacf125
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://ocsp.int-x3.letsencrypt.org
OCSP - must staple:no
Certificate Transparency:yes
Enhanced Key Usage:Server Authentication (1.3.6.1.5.5.7.3.1), Client Authentication (1.3.6.1.5.5.7.3.2)


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016
17.03.2021
expires in 218 days


2.
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
17.03.2016

17.03.2021
expires in 218 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA256 With RSA-Encryption
Serial Number:0A0141420000015385736A0B85ECA708
Thumbprint:E6A3B45B062D509B3382282D196EFE97D5956CCB
SHA256 / Certificate:JYR9Zo608E/dQLErawdAxWfafQJDCOtsLJb+QdneIY0=
SHA256 hex / Cert (DANE * 0 1):25847d668eb4f04fdd40b12b6b0740c567da7d024308eb6c2c96fe41d9de218d
SHA256 hex / PublicKey (DANE * 1 1):60b87575447dcba2a36b7d11ac09fb24a9db406fee12d2cc90180517616e8a18
SHA256 hex / Subject Public Key Information (SPKI):cbb93d32de628874a3ecfb92affadc97f1b795f84cc6f24221a089dee1aa25ad
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:http://isrg.trustid.ocsp.identrust.com
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000
30.09.2021
expires in 415 days


3.
CN=DST Root CA X3, O=Digital Signature Trust Co.
30.09.2000

30.09.2021
expires in 415 days


KeyalgorithmRSA encryption (2048 bit)
Signatur:SHA-1 with RSA Encryption
Serial Number:44AFB080D6A327BA893039862EF8406B
Thumbprint:DAC9024F54D8F6DF94935FB1732638CA6AD77C13
SHA256 / Certificate:BocmAzGnJAPZCfEF5pvPDTLhvSST/8bZIG0RvNZ3Bzk=
SHA256 hex / Cert (DANE * 0 1):0687260331a72403d909f105e69bcf0d32e1bd2493ffc6d9206d11bcd6770739
SHA256 hex / PublicKey (DANE * 1 1):563b3caf8cfef34c2335caf560a7a95906e8488462eb75ac59784830df9e5b2b
SHA256 hex / Subject Public Key Information (SPKI):29cc40db5e2de462a311cbbafaa1dc466960002335ecdf3317f2cd05c1d0bedf
SPKI checked via https://v1.pwnedkeys.com/spki-hash:Good: Key isn't compromised
OCSP - Url:
OCSP - must staple:no
Certificate Transparency:no
Enhanced Key Usage:



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
0
2

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1446169837
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-21 14:36:53
2020-05-21 14:36:53
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com - 2 entries


859207788
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-04-11 19:29:56
2019-07-10 19:29:56
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com - 2 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
0
2

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2491700999
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-02-21 13:36:53
2020-05-21 12:36:53
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com
2 entries


2248984519
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-12-11 15:18:17
2020-03-10 15:18:17
*.burp.triaxiomsecurity.com, burp.triaxiomsecurity.com
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:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
www.burp.triaxiomsecurity.com
-4

Not Implemented - The name server does not support the requested kind of query
1
0
burp.triaxiomsecurity.com
-4

Not Implemented - The name server does not support the requested kind of query
1
0
triaxiomsecurity.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
triaxiomsecurity.com

Refused - The name server refuses to perform the specified operation for policy reasons
1
0
burp.triaxiomsecurity.com

ok
1
0
www.burp.triaxiomsecurity.com

ok
1
0
_acme-challenge.burp.triaxiomsecurity.com


2
2
_acme-challenge.www.burp.triaxiomsecurity.com


2
2
_acme-challenge.burp.triaxiomsecurity.com.triaxiomsecurity.com


2
2
_acme-challenge.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com


2
2
_acme-challenge.www.burp.triaxiomsecurity.com.burp.triaxiomsecurity.com


2
2
_acme-challenge.www.burp.triaxiomsecurity.com.www.burp.triaxiomsecurity.com


2
2


15. Portchecks

No Port informations found. The feature is new (startet 2019-07-09), so recheck this domain.



Permalink: https://check-your-website.server-daten.de/?i=daef0ac0-3f74-44c5-88af-bb76d07c3ac1


Last Result: https://check-your-website.server-daten.de/?q=burp.triaxiomsecurity.com - 2020-03-26 01:19:21


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

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