Skip to content

Hostname

optix.pk

Last fetched

optix.pk resolves to 188.114.96.3, announced in 188.114.96.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. optix.pk 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 · optix.pkRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/optix.pk

Resolution chain

IPv6 resolution

Attribution

namecheap

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for optix.pk. 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
103-86-53-22.optix.pk
103-86-55-197.optix.pk
103-86-55-65.optix.pk
43-245-207-23.optix.pk
43-251-252-148.optix.pk
43-251-252-42.optix.pk
crm.optix.pk
intellidesk.optix.pk
speedtest.optix.pk
www.optix.pk

Showing 10 of 10 subdomains (10 per page).

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

  • brianna.ns.cloudflare.com
  • luciana.ns.cloudflare.com
  • nash.ns.cloudflare.com
  • wesley.ns.cloudflare.com

MX records

  • optix-pk.mail.protection.outlook.com
  • mail4.multinet.com.pk

SPF policy

  • include: sg1-ts103.a2hosting.com
  • include: spf.a2hosting.com
  • include: amazonses.com
  • include: spf.mailjet.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from optix.pk 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: "optix.pk"})-[: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.