netswork.us security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

41risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

4Medium

4Low

2Info

Collected 7 hours ago50.5sfrom cache

Certificate Transparency66
DNS resolution21
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs15
Registration
DNS posture6
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis10

noteFound 66 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.
noteNo registration data: RDAP has no record at this level.
note1 host was identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://netswork.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://netswork.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://netswork.com/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: netswork.us
test.netswork.us appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test.netswork.us
www.test.netswork.us appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: www.test.netswork.us
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://netswork.com/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: netswork.us
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: netswork.us
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: netswork.us

final https://netswork.com/status 200time 1830msstack cloudflare · WordPress 7.0

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
netswork-us.mail.protection.outlook.com
!SPFends in ~all
v=spf1 include:cvphkbww6z.powerspf.com ~all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:cltnit4zeh@rua.powerdmarc.com; ruf=mailto:cltnit4zeh@ruf.powerdmarc.com; pct=100; fo=1;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓6 nameservers
ns10.netswork.us ns11.netswork.us ns12.netswork.us ns13.netswork.us ns14.netswork.us ns15.netswork.us

Address	Ports	Edge	Network
162.159.135.42 netswork.us +20	80443205220532082208320862087+5	Cloudflare~	—
35.74.128.84 mymail.netswork.us +1	80443	direct	—
212.69.158.109 3cx.netswork.us	none known	direct	—
212.69.158.114 vg1.netswork.us	none known	direct	—
12.208.190.209 voip.netswork.us	none known	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

netswork.us security report

Moderate

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames