All .YE domainspepa.com.ye

RISK ADVISORY: pepa.com.ye — .YE NAMESPACE & REGULATORY DEPENDENCY

.YE is not an open or politically neutral national namespace. The domain pepa.com.ye operates inside that namespace. Its registry, government subdomains, and core telecommunications and DNS infrastructure are administered through institutions under Houthi control in Sana’a. Ansarallah (the Houthis) is designated as a Foreign Terrorist Organization (FTO) and Specially Designated Global Terrorist (SDGT).

Government and official media domains operate as direct instruments of this system. Private, commercial, and civic registrants also depend entirely on approval, registration, renewal, licensing, connectivity, DNS resolution, and enforcement mechanisms controlled by the same authorities.

The continued operation of pepa.com.ye must therefore be treated as a material Houthi-controlled infrastructure and regulatory dependency, even where available evidence does not establish that the individual registrant is directly Houthi-owned or ideologically aligned.

Organizations interacting with an entity using pepa.com.ye should independently verify the registrant’s legal entity, beneficial ownership, payment routes, hosting infrastructure, and exposure to registry-level interception or revocation before communicating, contracting, or transferring funds.

Evidence: IANA .YE delegation · U.S. Treasury designations · Human Rights Watch: Yemen · Registry control-chain findings

What is pepa.com.ye?

pepa.com.ye is a domain name under the com.ye public suffix in the public .YE evidence corpus. Evidence through 2026-10-09 records active technical evidence, 2 related hostnames, 7 confirmed DNS changes, 347 Common Crawl captures, 2 deployed TLS observations, a current screenshot, and linked WARC evidence.

Registry-control context

IANA currently lists TeleYemen as the .YE manager. ICANN's continued delegation keeps Yemen's national namespace operated through institutions under Houthi control. IANA delegation record; Control-chain evidence and analysis.

Record summary

Field	Public observation
Domain	`pepa.com.ye`
Public suffix	`com.ye`
Corpus status	Historical corpus and newly observed signals
New-domain observation	`certificate_transparency`, `common_crawl` · `2013-05-18`, `2026-08-28`
Observed technical state	`dns-records-present`
Public evidence through	2026-10-09

Registration evidence

Field	Public observation
Observed lifecycle dates	expiration: `2040-12-31` last_changed: `2024-04-25` registration: `2000-01-01`
Observed status values	`active`
Observed nameservers	—
Observed registrar	`Y.Net - Sales`

DNS and related hostnames

Related hostnames in the public catalog: 2

Hostname	DNS state	Address / alias	Mail / authority
`pepa.com.ye`	records_present	`195.200.9.107`, `2a02:4780:25:3e1c:91f2:b1fb:54bb:a51e`, `2a02:4780:35:3019:7999:9772:75bb:8c7c`, `89.116.109.168`	`10 mx2.hostinger.com`, `5 mx1.hostinger.com`, `ns1.dns-parking.com`, `ns2.dns-parking.com`
`www.pepa.com.ye`	records_present	`195.200.9.91`, `2a02:4780:25:68a4:3357:c87b:1927:e70a`, `2a02:4780:26:14bb:d822:893c:31c:993b`, `91.108.103.149`, `www.pepa.com.ye.cdn.hstgr.net`	—

Confirmed DNS change history

Changes are published only after two consecutive definitive observations. Timeouts, SERVFAIL and other inconclusive results do not create change events.

Date	Hostname	Record	Before → after	Review class
2026-10-08	`pepa.com.ye`	`soa_serial`	`2026100101` `2026100801`	`telemetry`
2026-10-01	`pepa.com.ye`	`soa_serial`	`2026092401` `2026100101`	`telemetry`
2026-09-25	`pepa.com.ye`	`soa_serial`	`2026091701` `2026092401`	`telemetry`
2026-09-18	`pepa.com.ye`	`soa_serial`	`2026091001` `2026091701`	`telemetry`
2026-09-11	`pepa.com.ye`	`soa_serial`	`2026090301` `2026091001`	`telemetry`
2026-09-04	`pepa.com.ye`	`soa_serial`	`2026082701` `2026090301`	`telemetry`
2026-08-27	`pepa.com.ye`	`soa_serial`	`2026082001` `2026082701`	`telemetry`

Latest successful full-page screenshot

Public-web and deployed TLS evidence

Field	Public observation
Common Crawl summary	347 captures · 42 collections · first / last `2013-05-18` / `2026-09-15`
Deployed TLS certificates	`pepa.com.ye` — TLSv1.3 — countryName=US/organizationName=Let's Encrypt/commonName=YE1 — validity `2026-08-25` / `2026-11-23` `www.pepa.com.ye` — TLSv1.3 — countryName=US/organizationName=Let's Encrypt/commonName=YE1 — validity `2026-08-25` / `2026-11-23`

Infrastructure relationships

Relationship	Connected public node	First / last seen
cname_to	`www.pepa.com.ye.cdn.hstgr.net`	2026-08-26 / 2026-10-08
contains_hostname	`pepa.com.ye`	2026-08-08 / 2026-10-08
contains_hostname	`www.pepa.com.ye`	2013-05-18 / 2026-10-08
delegated_to	`ns1.dns-parking.com`	2026-08-26 / 2026-10-08
delegated_to	`ns2.dns-parking.com`	2026-08-26 / 2026-10-08
mail_routed_to	`mx1.hostinger.com`	2026-08-26 / 2026-10-08
mail_routed_to	`mx2.hostinger.com`	2026-08-26 / 2026-10-08
observed_in_web_archive	`common-crawl`	2013-05-18 / 2026-09-12
observed_in_web_archive	`common-crawl`	2026-08-08 / 2026-09-15
presents_certificate	`98493a46fd74acfa98c079b0c3475b817ca11bec9d0ab772c98ddc3026d80965`	2026-09-12 / 2026-09-12
presents_certificate	`98493a46fd74acfa98c079b0c3475b817ca11bec9d0ab772c98ddc3026d80965`	2026-10-03 / 2026-10-03
registered_via	`R1-YE`	2026-08-26 / 2026-10-08

Archive evidence

Field	Public observation
Homepage WARC corpus	HTTP 200 · text/html · manifest

What this record proves

This record proves that the name is present in the cited public corpus and preserves its specific registration, current DNS, confirmed DNS-change, screenshot, web, certificate, relationship and archive observations listed above.

Sources and limitations

The master list is the union of a historical public corpus and newly observed public candidates. It is not an official zone file or a complete list of every .YE registration. Observations can be incomplete or stale; dates are shown at day precision.

`pepa.com.ye`