Domain · verified · Standard · no Deep · Mobile
9 hosts, 8 answering on the web · 10 open issues on them · last scan partial
Last scan Thu 15 Oct, 02:00 · 59% of requests slowed
So the last scan came back partial and closed nothing. Let our three addresses past rate limiting and bot checks; every other rule stays on.
How each host meets the internet
9 hosts that resolve · the top layer is what attackers reach first
Straight onto the internet
4 hosts1 meant to be internal
Its own address answers. Whatever it runs, attackers reach directly.
Behind your edge
4 hosts
Cloudflare or CloudFront answers first: a firewall and rate limits in front.
A name with nothing on the web
1 host
It resolves, but no website answers. Mail, or something forgotten.
Names that went quiet
7 hosts
Seen in certificate logs or DNS history, but they no longer resolve.
dev.tessellate.ngftp.tessellate.ngold.tessellate.ngshop.tessellate.ngstaging.tessellate.ngtest.tessellate.ngvpn.tessellate.ng
Four things answer straight from their own address. That's where an attacker starts, and two of them have open issues.
How much each mattersA crown jewelsB supports themC internal and brandD public information
Every host under tessellate.ng
9 hosts that resolve · owners come from CODEOWNERS, naming or by hand
How we scan it, and letting us through
1 schedule · behind Cloudflare
Schedules
The last scan
Only 41% of the vulnerability templates' requests completed, so a clean result there doesn't mean clean.
Our scanner comes from
User agent: SecureAssure-Scanner/2.4 (+https://secureassure.vernovi.io/scanner)
Cloudflare slowed 59% of our requests last scan. Let these addresses through and the next scan sees everything.
Letting us through
It's yours, and we keep checking
Verified Thu 17 Sep, 14:05 · rechecked every day
Keep the record in place. If a daily check stops finding it, Standard and Deep scans pause until it’s back, and this domain drops to the outside checks a vendor gets.