metraonline.com security report

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

58risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

5Low

1Info

Collected 14 hours ago30.7sfrom cache

Certificate Transparency5
DNS resolution8
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs30
Registration
DNS posture3
Email authentication0
Certificate
Security headers0
Archived URLs
Analysis11

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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.metraonline.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@metraonline.com"`, review the reports, then move to p=quarantine and p=reject.
asset: metraonline.com
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://www.metraonline.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://www.metraonline.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://www.metraonline.com/
Nothing tells receiving mail servers which hosts may send as @metraonline.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: metraonline.com
test.metraonline.com 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.metraonline.com
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.metraonline.com/
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://www.metraonline.com/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.metraonline.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: metraonline.com
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: metraonline.com

final https://www.metraonline.com/status 200time 1605msstack cloudflare

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

!Cookie XSRF-TOKEN
Secure · no HttpOnly · SameSite=lax
✓Cookie metra_dealer_session
Secure · HttpOnly · SameSite=lax
✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓3 nameservers
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com

✓Registered with Network Solutions, LLC26.8 years old
metraonline.com
✓Registration expiry1547 days
2030-12-02
✓Transfer lock
client transfer prohibited
✓3 nameservers at registry
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com

Address	Ports	Edge	Network
172.66.0.96 metraonline.com +5	80443205220532082208320862087+5	Cloudflare~	—
162.159.140.98 metraonline.com +5	80443205220532082208320862087+5	Cloudflare~	—
76.76.21.241 support.metraonline.com +3	80443	direct	—
66.33.60.193 support.metraonline.com +3	80443	direct	—

Archived URLs

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

metraonline.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames