Skip to content

Hostname

op-lab.fi

Last fetched

op-lab.fi is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. op-lab.fi is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · op-lab.fiRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.9/10canon.whisper.security/host/op-lab.fi

Resolution chain

No IPv4 resolution is recorded for op-lab.fi in WhisperGraph.

IPv6 resolution

No AAAA record for op-lab.fi is recorded in WhisperGraph.

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for op-lab.fi. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
cowork.op-lab.fi
ha.op-lab.fi
lomakepalvelu.op-lab.fi
ns1.op-lab.fi
ns2.op-lab.fi
ns3.op-lab.fi
ns4.op-lab.fi
testamentti.op-lab.fi
tuki.op-lab.fi
vader.op-lab.fi

Showing 10 of 13. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns-11.awsdns-01.com
  • ns-53.awsdns-06.com
  • ns-744.awsdns-29.net
  • ns-779.awsdns-33.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net
  • ns-1080.awsdns-07.org
  • ns-1172.awsdns-18.org
  • ns-1867.awsdns-41.co.uk
  • ns-1927.awsdns-48.co.uk

Threat-feed evidence

History

Related pages

Pivot from op-lab.fi into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "op-lab.fi"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.