rarenewspapers.com security report

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

36risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

1High

0Medium

10Low

2Info

Collected 8 hours ago7.4sfrom cache

Headers—

unavailable

Certificate Transparency22
DNS resolution20
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs22
Registration
DNS posture4
Email authentication1
Certificate
Security headers
Archived URLs
Analysis13

noteFound 22 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 16 addresses; enriching the first 12.
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.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.

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.rarenewspapers.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@rarenewspapers.com"`, review the reports, then move to p=quarantine and p=reject.
asset: rarenewspapers.com
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 208.109.76.53:25
stage.rarenewspapers.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: stage.rarenewspapers.com
v2.staging.rarenewspapers.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: v2.staging.rarenewspapers.com
v3.staging.rarenewspapers.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: v3.staging.rarenewspapers.com
staging-app.rarenewspapers.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: staging-app.rarenewspapers.com
metrics.stage.rarenewspapers.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: metrics.stage.rarenewspapers.com
stage-do-test.rarenewspapers.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: stage-do-test.rarenewspapers.com
stage-kamal-test.rarenewspapers.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: stage-kamal-test.rarenewspapers.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: rarenewspapers.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: rarenewspapers.com
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: rarenewspapers.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: rarenewspapers.com

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com aspmx.l.google.com aspmx2.googlemail.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com include:amazonses.com ip4:184.106.203.106 ip4:173.163.33.254 ip4:13.59.55.15 ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1303.awsdns-34.org ns-1617.awsdns-10.co.uk ns-193.awsdns-24.com ns-708.awsdns-24.net

✓Registered with Amazon Registrar, Inc.28.9 years old
rarenewspapers.com
!Registration expiry43 days
2026-10-21
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1303.awsdns-34.org ns-1617.awsdns-10.co.uk ns-193.awsdns-24.com ns-708.awsdns-24.net

Address	Ports	Edge	Network
208.109.76.53 blog.rarenewspapers.com +1	2580443	direct	—
3.132.102.92 stage.rarenewspapers.com +3	80443	direct	—
13.35.36.3 secure-images.rarenewspapers.com +3	80443	direct	—
13.35.36.87 secure-images.rarenewspapers.com +2	80443	direct	—
13.35.36.103 secure-images.rarenewspapers.com +2	80443	direct	—
13.35.36.10 secure-images.rarenewspapers.com +2	80443	direct	—
16.15.230.144 images.rarenewspapers.com +9	80443	direct	—
52.216.48.89 images.rarenewspapers.com +9	80443	direct	—
16.15.212.17 images.rarenewspapers.com +9	80443	direct	—
54.231.129.17 images.rarenewspapers.com +9	80443	direct	—
3.13.31.121 www.rarenewspapers.com +3	80	direct	—
31.97.210.67 design-review.rarenewspapers.com	none known	direct	—

Archived URLs

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

rarenewspapers.com security report

Moderate

Findings

Email authentication

DNS

Registration

Hosts

Hostnames